Online Developer Meeting (2024-11-26): Difference between revisions

From Octave
Jump to navigation Jump to search
(Create page)
 
(add potential topics)
Line 1: Line 1:
* Date: Tuesday, November 27, 2024 @ 18:00 UTC '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=11&day=22&hour=18&min=0&sec=0&p1=263&p2=37&p3=26&p4=176&p5=248&p6=108&p7=111&p8=264&p9=2322 Convert timezones here!]'''
* Date: Tuesday, November 27, 2024 @ 18:00 UTC '''[https://www.timeanddate.com/worldclock/meetingdetails.html?year=2024&month=11&day=22&hour=18&min=0&sec=0&p1=263&p2=37&p3=26&p4=176&p5=248&p6=108&p7=111&p8=264&p9=2322 Convert timezones here!]'''
* Location: https://meet.jit.si/octave-dev
* Location: https://meet.jit.si/octave-dev
== Today's topics ==
* Release of Octave 9.3.0?
* "Code sprint" for new terminal widget?
* buildbot: broken synchronization for stable branch?
* GitHub mirror: broken synchronization for stable branch? access permissions for organization members?


== Previous topics ==
== Previous topics ==
== Today's topics ==


* Digital Ocean server is still slow intermittently.
* Digital Ocean server is still slow intermittently.

Revision as of 09:22, 22 November 2024

Today's topics

  • Release of Octave 9.3.0?
  • "Code sprint" for new terminal widget?
  • buildbot: broken synchronization for stable branch?
  • GitHub mirror: broken synchronization for stable branch? access permissions for organization members?

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