Online Developer Meeting (2024-03-26)

Today's topics

Timing for next bugfix release (middle of April, say 4/15)
- bug #65476 (`mkoctfile -p LIBS` includes unnecessary libraries) Done
- Copyright dates for documentation, and possible MXE-Octave files out of date Done
OctConf 2024
- Agreed. Eastern North America likely. Rik will post a poll.
Roadmap and priorities for Octave 10
- Which important features to focus on for Octave 10?
- JWE is cleaning up the m-file exceptions
Discuss a potential timeline for native string class support

Status of 9.1 Release
- Are there remaining blocker bugs? -- None. In case of issues, a version 9.2 could be released early.
- Do we issue a second release candidate (RC2)? -- No RC2. jwe will proceed to create a release tarball for Octave 9.1 and the Windows installers shortly.
Common id tag for developer of Octave packages in AppStream Metainfo files?
- Should they use a different tag from the identifier of core Octave? See core patch and package change/discussion
- Conclusions: no strong feelings. Each package should generally decide what they want: if they feel that id="octave.org" and <name>Octave Community</name> describes their community, that's probably fine. If in doubt, just ask.
How to handle pull requests for the mirror on GitHub?
New bug reports on Savannah for packages should be tagged by the package name in parenthesis at the start of the report title. E.g., "(statistics) some error" (i.e., no longer prepend with "[octave forge]"). Also, set the report category to "Octave package". Try to CC package developers.