Editing Online Developer Meeting (2022-07-26)

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:


* GSoC progress
* GSoC progress
** Progress was presented by available mentors. Projects are on track.
** '''Progress was presented by available mentors. Generally good. Some discussion on openlibm, accepted that negative results are also valuable.'''
** Openlibm project concluded that the approach doesn't work. Valuable negative result!
* VM progress?
** libtiff project will probably implement the classdef as an .m file. (At least the constructor, which is hard/impossible to implement in C++ code. It is not a "normal" DLDFCN). Will probably move from dld to core (libtiff dependency).
** '''Petter presented updates on his VM.'''
* When should a new function go to core or load dynamically?
** '''jwe prefers incorporating that into the default branch of Octave as soon as practical, and let it remain off by default unless the user wants to enable it with a configure switch or a runtime switch'''
** If the dependencies are already linked into Octave core -> No big benefit to have it dynamically loaded. More sensible to add in core.
** '''This would be formed into an API for a generic VM approach to Octave that can be used for other VMs such as the Jitter one, etc'''
** If function loads a big (new) dependency, it might make sense to load it "on demand". --> dldfcn
* Octave packages progress update
* VM progress:
* Managing diversity of libraries (libm, libc etc)
** Petter presented updates on his VM. Good progress. But still a lot to do.
** See [https://octave.discourse.group/t/point-of-openlibm-project-or-if-even-julia-wants-to-shift-away-from-openlibm-do-we-want-to-use-it/2980/  background]
** will incrementally move from fork to default branch as an experimental feature with a configure option to disable it.
** will most likely not be active by default in Octave 8 (either not compiled or de-activated on run-time)
** won't stop the option for alternative VM implementations. Might help to define an "API" for other VM implementations (like Jitter, etc).
* Release process for Octave 7.2:
* Release process for Octave 7.2:
** About 10 (actual) changes since the last release candidate (about 6 weeks ago). Should we make a second release candidate?
** About 10 (actual) changes since the last release candidate (about 6 weeks ago). Should we make a second release candidate?
*** No new release candidate. Proceed with a release after some final preparations (e.g., NEWS file).
** Not much feedback for the first release candidate. Should we skip making release candidates entirely and directly make releases? Should we announce them more prominently (e.g., on the web page)?
** Not much feedback for the first release candidate. Should we skip making release candidates entirely and directly make releases? Should we announce them more prominently (e.g., on the web page)?
*** Call for ideas.
* Octave packages progress update
* Managing diversity of libraries (libm, libc etc)
** See [https://octave.discourse.group/t/point-of-openlibm-project-or-if-even-julia-wants-to-shift-away-from-openlibm-do-we-want-to-use-it/2980/  background]
* Octave 7.3 and 8 timeline?
* Octave 7.3 and 8 timeline?


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)