Online Developer Meeting (2023-05-23): Difference between revisions

From Octave
Jump to navigation Jump to search
Line 6: Line 6:
* VM update and planning:
* VM update and planning:
** Add to default by Jun 30, giving 5-6 months of wider testing?
** Add to default by Jun 30, giving 5-6 months of wider testing?
* [https://octave.discourse.group/t/4440 New warnings from GCC 13.1] (GUI threading issue?)


== Previous topics ==
== Previous topics ==

Revision as of 10:03, 22 May 2023

Today's topics

  • GSoC updates
  • VM update and planning:
    • Add to default by Jun 30, giving 5-6 months of wider testing?
  • New warnings from GCC 13.1 (GUI threading issue?)

Previous topics

  • Octave 8.2.0 released
    • Release process went pretty smoothly.
    • If no specific extraordinary motivation, we won't need release candidates for future bug-fix releases.
    • @jwe will try to provide existing helper scripts and instructions for release process.
  • Coding Community Events
    • OctConf 2023?
      • @jwe proposed to do that in the form of a developer summit for a couple of days.
      • @Rik offered to open a poll for dates/venue/... on the discourse forum.
      • Probably, at least 6 months lead time.
    • Online coding sprints?
      • Maybe in the form of a loose online meeting for the duration of a weekend?
      • @Rik offered to open a poll for dates/tools/... on the discourse forum.
  • GSoC discussion
    • Process for evaluation of student applications has started.
    • Some promising candidates.
  • Possible version 9 projects:
    • Qt6 (does that force us to require a C++17 compiler?)
      • Only enablement patches have landed so far. Further integration and bug fixes are still needed.
    • new terminal widget
    • arguments blocks
    • improved breakpoint handling
    • experimental stack-based virtual machine
    • MException object
    • string object (separate from having double-quoted characters create string objects)
    • HDF5-based save and load compatible with Matlab's file format
    • refactor octave_function and classes derived from it
    • broadcasting for sparse
    • make graphics and GUI event processing in the interpreter independent from readline
  • Status of Octave Forge
    • should the Octave bug tracker continue to be used for reporting bugs in external packages?
      • Propose package maintainers to move to own trackers.
    • if not, how can we make it easy to find the location to report bugs for a package/package function? How do other systems like Python, R, etc., handle this problem?
  • Some old bug reports have been closed recently - thanks!
    Current stats by year:
2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 total
Octave 1 16 16 41 79 101 160 129 180 201 132 126 117 54 1353
Octave Forge 3 9 19 27 38 28 39 54 44 49 16 326

See also

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2023-05-23)&oldid=14805"