263
edits
(→Today's topics: GSoC 2025) |
|||
Line 19: | Line 19: | ||
** 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>? | ||
* 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] | * 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; reply received on 2025/03/19 promising an update "as quickly as possible"] | ||
* 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. |