244
edits
Online Developer Meeting (2023-04-25): Difference between revisions
Jump to navigation
Jump to search
→Today's topics: Add some notes from meeting
m (Add topic on community events) |
(→Today's topics: Add some notes from meeting) |
||
| Line 5: | Line 5: | ||
* Octave 8.2.0 released | * 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 | * Coding Community Events | ||
** OctConf 2023? | ** 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? | ** 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 | * GSoC discussion | ||
** Process for evaluation of student applications has started. | |||
** Some promising candidates. | |||
* 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?) | ||
*** Only enablement patches have landed so far. Further integration and bug fixes are still needed. | |||
** new terminal widget | ** new terminal widget | ||
** <tt>arguments</tt> blocks | ** <tt>arguments</tt> blocks | ||
| Line 23: | Line 34: | ||
* 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? | ||
*** 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? | ** 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: | ||