Online Developer Meeting (2025-08-26): Difference between revisions

Online Developer Meeting (2025-08-26) (view source)

170 bytes added , 26 August

m

Add commentary on discussion topics

1,217

edits

@@ Line 4: / Line 4: @@
 == Today's topics ==
-* Prepare release of Octave 10.3.0? 33 "actual" changes on the stable branch since the release of Octave 10.2.0 (ignoring, e.g., changes to the CI rules or reverted changes), 7 of which are documentation only.
+* Prepare release of Octave 10.3.0? 33 "actual" changes on the stable branch since the release of Octave 10.2.0 (ignoring, e.g., changes to the CI rules or reverted changes), 7 of which are documentation only.  '''Markus will start release process as time permits'''
 ** Any pending changes or bugs that need to be fixed for the stable branch?
-bug #67459 (clear ?)
+bug #67459 (clear ?) '''jwe has a potential fix.  He will test and commit before 10.3 release'''
-* Should Octave be built without debugging code for parser by default?
+* Should Octave be built without debugging code for parser by default?  '''Yes.  Rik will work on this.'''
 The debugging code is always there and always enabled.  For every statement parsed there is a check on the the parse_debug_flag to see whether debugging information should be printed.  But, this is really infrequently used code.  I have turned on the debugger in the parser just once in 10 years.  To me, this is specialist code that could be enabled by a developer during configuration or with a `-D` option to `cpp`, but ordinary users will never need this.