Online Developer Meeting (2024-09-24): Difference between revisions

Latest revision as of 06:35, 26 September 2024

GSoC:
- The projects that Andreas mentored successfully finished.
- No information on the project that Colin mentored during the meeting.
Plans for Octave 9.3.0:
- Target for merging the default branch to the stable branch in 6-8 weeks.
- Postpone decision about releasing 9.3.0 for a few more weeks.
Targets for Octave 10:
- Given the remaining time until the branches are merged, implementing Table or String classes for Octave 10 might not be reasonable.
- Implementing the arguments block might also be too large.
- Maybe, go ahead and merge the changes for the command window widget from here: https://octave.discourse.group/t/new-command-window-widget/501/82 (or the modified version from the following comment)
Thoughts about liboctmex:
- Go ahead and apply for Octave 10
- Maybe consider versioned symbols instead of bumping the SOVERSION for ABI/API breaking changes in the future?
Visibility attributes:
- Many (member) functions are marked (as opposed to the entire class) to allow for inline definitions of (member) functions in headers.
- Might still be incomplete (probably less complete in liboctinterp than in liboctave)
Virtual OctConf. Is it happening?

@@ Line 4: / Line 4: @@
 == Today's topics ==
-* GSoC?
+* GSoC:
-* Plans for Octave 9.3.0?
+** The projects that Andreas mentored successfully finished.
-* Thoughts about liboctmex?
+** No information on the project that Colin mentored during the meeting.
+* Plans for Octave 9.3.0:
+** Target for merging the default branch to the stable branch in 6-8 weeks.
+** Postpone decision about releasing 9.3.0 for a few more weeks.
+* Targets for Octave 10:
+** Given the remaining time until the branches are merged, implementing Table or String classes for Octave 10 might not be reasonable.
+** Implementing the arguments block might also be too large.
+** Maybe, go ahead and merge the changes for the command window widget from here: https://octave.discourse.group/t/new-command-window-widget/501/82 (or the modified version from the following comment)
+* Thoughts about liboctmex:
+** Go ahead and apply for Octave 10
+** Maybe consider versioned symbols instead of bumping the SOVERSION for ABI/API breaking changes in the future?
+* Visibility attributes:
+** Many (member) functions are marked (as opposed to the entire class) to allow for inline definitions of (member) functions in headers.
+** Might still be incomplete (probably less complete in liboctinterp than in liboctave)
 * Virtual OctConf. Is it happening?