Editing Online Developer Meeting (2023-04-25)
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
* Octave 8.2.0 released | * Octave 8.2.0 released | ||
* Coding Community Events | * Coding Community Events | ||
** OctConf 2023? | ** OctConf 2023? | ||
** Online coding sprints? | ** Online coding sprints? | ||
* GSoC discussion | * GSoC discussion | ||
* Possible version 9 projects: | * Possible version 9 projects: | ||
** Qt6 (does that force us to require a C++17 compiler?) | ** Qt6 (does that force us to require a C++17 compiler?) | ||
** new terminal widget | ** new terminal widget | ||
** <tt>arguments</tt> blocks | ** <tt>arguments</tt> blocks | ||
Line 34: | Line 23: | ||
* Status of Octave Forge | * Status of Octave Forge | ||
** should the Octave bug tracker continue to be used for reporting bugs in external packages? | ** should the Octave bug tracker continue to be used for reporting bugs in external packages? | ||
** 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? | ** 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 - <b>thanks!</b><br>Current stats by year: | * Some old bug reports have been closed recently - <b>thanks!</b><br>Current stats by year: |