1,174
edits
Online Developer Meeting (2025-03-25): Difference between revisions
Jump to navigation
Jump to search
m
Tweak text
m (→Today's topics) |
m (Tweak text) |
||
| Line 7: | Line 7: | ||
** What's left? Ready to release? | ** What's left? Ready to release? | ||
** What about packages (not core Octave)? Are they ready? | ** What about packages (not core Octave)? Are they ready? | ||
*** I know that financial package does not work, and that update is very simple (replace <code>.+</code> with <code>+</code>. | |||
* Discussion on continued use of Savannah Bug Tracker | * Discussion on continued use of Savannah Bug Tracker | ||
** Latest motivation to find something better is the inability to search for bug reports for old releases | ** Latest motivation to find something better is the inability to search for bug reports for old releases. | ||
* New name for <code>-forge</code> option to <code>pkg</code>? | * New name for <code>-forge</code> option to <code>pkg</code>? | ||
** 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. | ||
* Shared library versioning and <code>api-v60</code> tag | * Shared library versioning and <code>api-v60</code> tag | ||
** Is Octave's own internal api tag required anymore? | ** Is Octave's own internal api tag required anymore? | ||
** Does <code>liboctmex</code> need to check version anymore? Or is this already handled by <code>oct-shlib.cc</code> | ** Does <code>liboctmex</code> need to check version anymore? Or is this already handled by <code>oct-shlib.cc</code>? | ||
== Previous topics == | == Previous topics == | ||