Editing Online Developer Meeting (2023-04-25)

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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
** 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 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?
*** 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:
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)