1,174
edits
Online Developer Meeting (2025-03-25): Difference between revisions
Jump to navigation
Jump to search
m
Tweak text
m (Add commentary) |
m (Tweak text) |
||
| Line 5: | Line 5: | ||
* Octave 10.1.0 release | * Octave 10.1.0 release | ||
** What's left? Ready to release? [ | ** What's left? Ready to release? ['''Ready to release'''] | ||
*** Apply patch to make HTML and Qt documentation pretty? Or wait until first bug fix release? [ | *** Apply patch to make HTML and Qt documentation pretty? Or wait until first bug fix release? ['''Yes, apply patch'''] | ||
** What about packages (not core Octave)? Are they ready? [ | ** What about packages (not core Octave)? Are they ready? ['''Release Octave. Package maintainers will need to catch up'''] | ||
*** I know that financial package does not work, and that update is very simple (replace <code>.+</code> with <code>+</code>).[ | *** I know that financial package does not work, and that update is very simple (replace <code>.+</code> with <code>+</code>).['''Rik will prepare patch and submit to Patch Tracker'''] | ||
* New name for <code>-forge</code> option to <code>pkg</code>? [ | * New name for <code>-forge</code> option to <code>pkg</code>? ['''Yes. Start a Discourse thread to suggest a new name. "-forge" argument will persist, possibly forever'''] | ||
** Existing name implies SourceForge, and there are many other package repositories in use. | ** Existing name implies SourceForge, and there are many other package repositories in use. | ||
** Any change would need to see the <code>-forge</code> option persist for a very long time. | ** Any change would need to see the <code>-forge</code> option persist for a very long time. | ||