Online Developer Meeting (2022-10-25): Difference between revisions

→‎Today's topics: Update with notes from discourse
No edit summary
(→‎Today's topics: Update with notes from discourse)
 
Line 6: Line 6:
This month's meeting notes https://octave.discourse.group/t/octave-developer-meeting-october-2022/3512.
This month's meeting notes https://octave.discourse.group/t/octave-developer-meeting-october-2022/3512.


* 7.3 release activities
* Fosshost is currently down with no ETA for coming back. It doesn't look like their availability meets our expectations. Some domains could be moved on short term to other hosts or mirrors. Mid-term, we'd like to move to a different host (e.g., Dreamhost). Ask NumFOCUS if sponsoring would be possible.
* 8.1 release activities
Moving the buildbot host and hg repositories might be highest priority.
* Ongoing technical work: string type
* Octave 7.3.0 will likely be released during the next week (without a release candidate). Lacking access to the MXE Octave repository (host down), JWE will ask John Donoghue if he has a local checkout of the repository that he could supply.
** Any warnings to users about upcoming changes?
* Preparations for Octave 8: The default branch will likely get merged to the stable branch early in November. There was no major refactoring this time. So, we hope for a smooth release process.
* It would be nice to get more testers that could check if bug reports can be closed as fixed. They don't need to be maintainers. Anyone could possibly help (preferably on a variety of platforms). Arun Giridhar reached out on Discourse.
* A variety of different (larger) projects were discussed that are candidates for being added for Octave 8. Most of these projects need interested developers that are willing to spend some time in implementing and helping to maintain those features.
* A particular focus was on the <code>string</code> class (again). It might be a candidate for an early addition during the development cycle of Octave 9 (taking leverage of Andrew Janke's .m file implementation in the tablicious package). Having that might allow adapting a range of functions to accepting <code>string</code> objects early on (even if a "final" implementation of the <code>string</code> class might be in C++). Decisions for how to transition to the new syntax for double quotes still need to be taken.
* Other larger features include: a refactoring of the load path implementation, HDF5 interface for saving variables to files, implementation for saving <code>classdef</code> objects to files (probably only using that HDF5 interface), various improvements of the <code>classdef</code> implementation (e.g., better handling of arrays of <code>classdef</code> objects), <code>input</code> handling for the new experimental cross-platform command widget, and many more...
* If possible, it would be nice if all of these projects could be split into smaller, more feasible sub-projects.
 
* Ongoing technical work: dictionary / associative array
* Ongoing technical work: dictionary / associative array
** Waiting on strings
** Waiting on strings
216

edits