Latest revision |
Your text |
Line 1: |
Line 1: |
| * Date: Tuesday, Jul 26, 2022 @ 18:00 UTC | | * Date: Tuesday, Jul 26, 2022 @ 18:00 UTC |
| * Location: https://meet.jit.si/octave-dev | | * Location: https://meet.jit.si/octave-dev |
|
| |
| == Today's 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.
| |
| * 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?
| |
|
| |
| == Previous topics ==
| |
|
| |
| * Octave 7.2
| |
| ** jwe indicated a release is imminent
| |
| * VM updates
| |
| ** Presentations by mnabipoor and Petter
| |
| ** Both efforts will move forward
| |
| ** Need to define VM language
| |
| * Fosshost and hosting updates
| |
| ** Kai presented details of migration and documentation of the migration process
| |
| * [https://github.com/gnu-octave/MinusForge MinusForge] to finally move to Octave Packages with <code>pkg install -forge</code>
| |
| ** Timeline to deprecate https://octave.sourceforge.org.
| |
| ** Kai presented this new mechanism to obtain "pkg install -forge" functionality for GitHub packages in addition to SourceForge, en route to leaving SourceForge
| |
| * GSOC status/progress check-in
| |
| * Follow up on implementing classdef classes in C++
| |
| ** jwe presented updates on the classdef functionality.
| |
|
| |
| == See also ==
| |
|
| |
| * Next meeting: [[Online Developer Meeting (2022-08-23)]]
| |
| * Last meeting: [[Online Developer Meeting (2022-06-28)]]
| |
|
| |
| [[Category:2022]]
| |
| [[Category:Meetings]]
| |