1,174
edits
(Create new page) |
m (Add agenda item) |
||
Line 5: | Line 5: | ||
* Octave 10.1.0 release | * Octave 10.1.0 release | ||
** What's left? Ready to release? | |||
** What about packages (not core Octave)? Are they ready | |||
* 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>? | |||
** 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 | |||
* Shared library versioning and <code>api-v60</code> tag | |||
** 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> | |||
== Previous topics == | == Previous topics == |
edits