Online Developer Meeting (2022-08-23): Difference between revisions

From Octave
Jump to navigation Jump to search
(started page)
 
Line 12: Line 12:
** '''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'''
** '''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'''
** '''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'''
** '''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'''
* 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?
** 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)?
* Classdef
** '''Technical discussion happened on things specific to classdefs'''
* Octave packages progress update
* Octave packages progress update
* Managing diversity of libraries (libm, libc etc)
* 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]
** 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]
* 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?
** 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)?
* Octave 7.3 and 8 timeline?
* Octave 7.3 and 8 timeline?


Revision as of 19:20, 26 July 2022

Today's topics

Previous topics

  • GSoC progress
    • Progress was presented by available mentors. Generally good. Some discussion on openlibm, accepted that negative results are also valuable.
  • VM progress?
    • Petter presented updates on his VM.
    • 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
    • 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
  • 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?
    • 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)?
  • Classdef
    • Technical discussion happened on things specific to classdefs
  • Octave packages progress update
  • Managing diversity of libraries (libm, libc etc)
  • Octave 7.3 and 8 timeline?

See also

Retrieved from "https://wiki.octave.org/wiki/index.php?title=Online_Developer_Meeting_(2022-08-23)&oldid=14430"