Online Developer Meeting (2025-04-22)

From Octave
Jump to navigation Jump to search

Today's topics

  • 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 float types). How should this be handled?
    • Java 1.9 or higher is now required for Octave 11. How to check at run-time in initialize_jvm that JVM is adequate?
      • tactic #1: initialize JVM and call FindClass("java/lang/ref/Cleaner") 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)
  • 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

  • Octave 10.1.0 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? [Yes, apply patch]
    • 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 .+ with +).[Rik will prepare patch and submit to Patch Tracker]
  • New name for -forge option to pkg? [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.
    • Any change would need to see the -forge option persist for a very long time.
  • Shared library versioning and api-v60 tag
    • Is Octave's own internal api tag required anymore? [Apparently, yes. While shared library versioning will probably work on Linux, libraries on Windows do not have the same CURRENT:REVISION:AGE structure]
    • Does liboctmex need to check version anymore? Or is this already handled by oct-shlib.cc OCTAVE_API_VERSION is only used to check version match when loading .oct files. This may only matter on systems that don't have proper library versioning. But even on those systems, we might be able to perform a check based on shared library versions stored in the .oct file instead of using OCTAVE_API_VERSION.
  • 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". jwe will ping them again]
  • GSoC 2025: Proposal Deadline on April 8 [Conversation between Nick and Nir over whether to do GSOC this year]

See also

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2025-04-22)&oldid=15392"