Online Developer Meeting (2022-08-23): Difference between revisions
Jump to navigation
Jump to search
ArunGiridhar (talk | contribs) (→Previous topics: Move in updated notes from previous meeting) Tags: Mobile edit Mobile web edit |
ArunGiridhar (talk | contribs) (→Today's topics: Adding tentative agenda topics) Tags: Mobile edit Mobile web edit |
||
Line 3: | Line 3: | ||
== Today's topics == | == Today's topics == | ||
* VM activities? | |||
* GSoC activities | |||
* 7.2 release? | |||
== Previous topics == | == Previous topics == |
Revision as of 23:04, 26 July 2022
- Date: Tuesday, Aug 23, 2022 @ 18:00 UTC
- Location: https://meet.jit.si/octave-dev
Today's topics
- VM activities?
- GSoC activities
- 7.2 release?
Previous topics
- GSoC progress
- Progress was presented by available mentors. Projects are on track.
- Openlibm project concluded that the approach doesn't work. Valuable negative result!
- 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).
- When should a new function go to core or load dynamically?
- If the dependencies are already linked into Octave core -> No big benefit to have it dynamically loaded. More sensible to add in core.
- If function loads a big (new) dependency, it might make sense to load it "on demand". --> dldfcn
- VM progress:
- Petter presented updates on his VM. Good progress. But still a lot to do.
- 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:
- 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)?
- Call for ideas.
- About 10 (actual) changes since the last release candidate (about 6 weeks ago). Should we make a second release candidate?
- Octave packages progress update
- Managing diversity of libraries (libm, libc etc)
- See background
- Octave 7.3 and 8 timeline?
See also
- Next meeting: Online Developer Meeting (2022-09-27)
- Last meeting: Online Developer Meeting (2022-07-26)