Online Developer Meeting (2024-11-26)

From Octave
Revision as of 18:23, 26 November 2024 by Rik (talk | contribs) (Update items that are completed)
Jump to navigation Jump to search

Today's topics

  • Release of Octave 9.3.0?
    • Rik volunteered to shadow jwe while he makes release to learn the process. Markus and NickJ may also shadow event if the timing works out.
  • "Code sprint" for new terminal widget?
  • buildbot: broken synchronization for stable branch?
    • Apparently this fixed itself. Will monitor the situation.
  • GitHub mirror: broken synchronization for stable branch? access permissions for organization members?
    • Fixed by Kai on Nov. 25th.
  • load path and PKG_ADD issues
  • future of octave-cli (also: FLTK, and gnuplot graphics)

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

See also