Online Developer Meeting (2024-04-23): Difference between revisions

From Octave
Jump to navigation Jump to search
(Add reference to potential blocker)
Line 4: Line 4:
== Today's topics ==
== Today's topics ==
* Timing for next bugfix release
* Timing for next bugfix release
** potential blocker(?): [https://savannah.gnu.org/bugs/index.php?65605 bug #65605]: Octave call to function figure(); results in segfault with Qt6 6.7.0
* GSoC projects
* GSoC projects
* OctConf 2024
* OctConf 2024

Revision as of 08:10, 22 April 2024

Today's topics

  • Timing for next bugfix release
    • potential blocker(?): bug #65605: Octave call to function figure(); results in segfault with Qt6 6.7.0
  • GSoC projects
  • OctConf 2024
  • Roadmap and priorities for Octave 10
  • Discuss a potential timeline for native string class support
  • Should we make and distribute nightly builds for Windows for the default branch?
  • Octave in MSYS2 (binary distributor for Windows MinGW)

Previous topics

  • Timing for next bugfix release (middle of April, approx. one month after the 9.1.0 release)
    • bug #65476 (`mkoctfile -p LIBS` includes unnecessary libraries) Done
    • Copyright dates for documentation, and possible MXE-Octave files out of date Done
    • In the future, we'll likely aim for a .2.0 release around a month after the .1.0 release; a .3.0 around 3 month after the .1.0 release; and a .4.0 release about 6 months after the .1.0 release. If necessary, additional releases are possible in between or after these approximate dates, or some releases could be skipped.
  • Andreas Bertsatos will open a thread about extracting demos from classdef files [1]
  • OctConf 2024
    • Agreed. Eastern North America likely. Rik will post a poll.
  • Roadmap and priorities for Octave 10
    • Which important features to focus on for Octave 10?
    • JWE will try to make MExceptions real classdef objects (not overloadable, fully implemented in C++)
    • JWE will try to start a thread on Discourse about potential new features for Octave 10.
  • Discuss a potential timeline for native string class support

See also