Difference between revisions of "Online Developer Meeting (2022-07-26)"

From Octave
Jump to navigation Jump to search
(→‎Previous topics: Add dates & categories)
Tags: Mobile edit Mobile web edit
 
(6 intermediate revisions by 2 users not shown)
Line 5: Line 5:
  
 
* GSoC progress
 
* GSoC progress
* VM progress
+
** Progress was presented by available mentors. Projects are on track.
* Octave packages progress
+
** Openlibm project concluded that the approach doesn't work. Valuable negative result!
* Octave 7.3 and 8 timeline
+
** 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 ==
 
== Previous topics ==
Line 28: Line 45:
 
== See also ==
 
== See also ==
  
* Next meeting: [[Online Developer Meeting (2022-08-30)]]
+
* Next meeting: [[Online Developer Meeting (2022-08-23)]]
 
* Last meeting: [[Online Developer Meeting (2022-06-28)]]
 
* Last meeting: [[Online Developer Meeting (2022-06-28)]]
  
 
[[Category:2022]]
 
[[Category:2022]]
 
[[Category:Meetings]]
 
[[Category:Meetings]]

Latest revision as of 19:37, 26 July 2022

Today's topics[edit]

  • 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)
  • Octave 7.3 and 8 timeline?

Previous topics[edit]

  • 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
  • MinusForge to finally move to Octave Packages with pkg install -forge
    • 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[edit]