Online Developer Meeting (2021-12-28)

Revision as of 16:32, 27 December 2021 by Mmuetzel (talk | contribs) (Add previous topics and some new topic suggestions.)

Todays topics

  • Meet and greet 5 minutes before meeting (audio testing).

Release process of Octave 7.1

  • Any blocking issues?
  • Translations?
  • Time for a first release candidate?

Update strategy for MXE Octave

  • default branch was merged to release a couple of weeks ago. That was meant to get the CI working after the merge from default to stable in the main Octave repository. It was not meant to freeze the branch...
  • When should the "actual" merge happen? For the (firs?) release candidate? For the final release?

Previous topics

The following items were not discussed. Just some links to progress on those items are displayed.

Octave 7

MXE Octave merge strategy

  • When should the default branch of MXE Octave be merged to the release branch?
    • Around the same time as the merge of the default branch of Octave to its stable branch.
  • Which branches should the buildbots use in the pre-release phase? Different for jwe's buildbots and octave.space?
    • Keep them running like they are. Evaluate if buildbot failures need action in the transition period before the major release.

UCRT version of Octave?

Bus factor

Octave 8 ideas

  • jwe updated Category:Development#jwe_priorities and clean up outdated JWE Project Ideas.
  • jwe wants to work on argument-list syntax.
  • rik wants to consistently use OCTAVE_LOCAL_BUFFER in liboctave.
  • OpenMP parallelization for trivial cases (e.g. initialize matrix with constant)?
    • Ensure thread safeness of Array classes (especially GUI-interpreter communication)
    • Maybe based on std:shared_ptr? But they aren't guaranteed to be thread-safe by design either.
    • Eliminate mutable class data.
  • Other performance improvements:
    • Idea: memory pools: bug #57321
    • Idea: static_cast vs. dynamic_cast: patch #10139
    • General remark: Prefer standard features instead of "reinventing the wheel" by implementing intricate optimizations.

See also