1,173
edits
Online Developer Meeting (2025-03-25): Difference between revisions
Jump to navigation
Jump to search
m
Tweak text
m (Add agenda item) |
m (Tweak text) |
||
| Line 8: | Line 8: | ||
** 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>). | *** I know that financial package does not work, and that update is very simple (replace <code>.+</code> with <code>+</code>). | ||
* 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. | ||
* Run-time checks for adequate libraries | * Run-time checks for adequate libraries | ||
** BLAS library can be correct at compile-time, but switched at run-time to one that is not (MacOS and functions with <code>float</code> types). How should this be handled? | ** BLAS library can be correct at compile-time, but switched at run-time to one that is not (MacOS and functions with <code>float</code> types). How should this be handled? | ||
| Line 21: | Line 16: | ||
*** tactic #1: initialize JVM and call <code>FindClass("java/lang/ref/Cleaner")</code> and then tear down JVM if it is not adequate. | *** tactic #1: initialize JVM and call <code>FindClass("java/lang/ref/Cleaner")</code> and then tear down JVM if it is not adequate. | ||
*** tactic #2: check Java version number against 1.9 before initializing (but may be difficult to have cross-platform compatibility) | *** tactic #2: check Java version number against 1.9 before initializing (but may be difficult to have cross-platform compatibility) | ||
* * Sloppy Numfocus website? (https://numfocus.org/project/gnu-octave). Clicking on Octave logo goes to galaxyproject.org, not Octave web site. '''[1. Top logo should point to octave.org, 2. Contribute code logo should point to Get Involved page, 3. Bottom logo should point to website, not Mercurial archive]''' [jwe wrote e-mail, but website is still not updated as of 2025/03/23] | * 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>? | |||
* Sloppy Numfocus website? (https://numfocus.org/project/gnu-octave). Clicking on Octave logo goes to galaxyproject.org, not Octave web site. '''[1. Top logo should point to octave.org, 2. Contribute code logo should point to Get Involved page, 3. Bottom logo should point to website, not Mercurial archive]''' [jwe wrote e-mail, but website is still not updated as of 2025/03/23] | |||
* 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. | |||
== Previous topics == | == Previous topics == | ||