Online Developer Meeting (2024-10-22)

• Date: Tuesday, October 22, 2024 @ 18:00 UTC Convert timezones here!
• Location: https://meet.jit.si/octave-dev

Today's topics

• Digital Ocean server is still slow intermittently.
  • At the time of the meeting, CPU load was 48 (100%)
  • Looking at the logs, the situation improved though.
  • Large number of Python processes (mainly for the web interface for hg.octave.org) are the main contributors to CPU load. Maybe, disable https access to hg.octave.org (only leave SSH)?

• Octave 9.3.0:
  • Ready for release
  • jwe will start the release process shortly.
  • Could a person shadow jwe during that process to get an idea which steps are involved and could potentially to releases themselves?

• Start process for Octave 10:
  • Merge default to stable (when?)
    • Maybe, delay the merge until the experimental command window widget is in a more usable state? Main blockers include: input blocks Octave indefinitely, displaying large output is very slow.
    • Tried to find "quick fix" for existing command window widget with limited (or no) success. Maybe, reach out to Microsoft developers at https://github.com/microsoft/terminal/issues/17054
    • Summary is still: https://octave.discourse.group/t/merging-branches-for-octave-9/4978/40
  • Update gnulib
  • Pending changes?

• To improve coverage for mkoctfile, should we include building some Octave packages in CI? (Maybe, the "stk" package because it builds .mex files, and the "control" package because it builds .oct files with C++ and Fortran?)
  • Also run tests for these packages in CI?
  • Fix version? Or always latest version from package index?

Previous topics

• 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?

See also

• Next meeting: Online Developer Meeting (2024-11-26)
• Prev meeting: Online_Developer_Meeting_(2024-09-24)