Changes

Jump to navigation Jump to search
Add previous topics and some new topic suggestions.
Line 6: Line 6:  
* Meet and greet 5 minutes before meeting (audio testing).
 
* Meet and greet 5 minutes before meeting (audio testing).
   −
=== Topic 1 ===
+
=== Release process of Octave 7.1 ===
   −
* Point 1
+
* Any blocking issues?
 +
* Translations?
 +
* Time for a first release candidate?
 +
 
 +
=== Update strategy for MXE Octave ===
 +
 
 +
* <code>default</code> branch was merged to <code>release</code> a couple of weeks ago. That was meant to get the CI working after the merge from <code>default</code> to <code>stable</code> 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 ===
 +
 
 +
* Octave 7.1.0 release activities and timeline
 +
** [[7.1 Release Checklist]]
 +
** Merge default to stable now
 +
** '''No new features anymore''' (explain on Octave Discourse @jwe?)
 +
*** Focus on stabilization
 +
*** Bugs to be fixed marked on Savannah with "7.0.90" or "Octave 7" on https://octave.space/savannah/
 +
** Go through "ready for test" list, close as much as possible
 +
** Call for translations
 +
*** https://octave.discourse.group/t/how-to-update-the-gui-translation-files/1834
 +
** Approx. final release date (early 2022)
 +
 
 +
=== 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? ===
 +
 
 +
* Should we distribute an UCRT version of Octave for Windows?
 +
** No big opposition to adding new versions if it doesn't become too many and they add value.
 +
** Probably changes inside Octave necessary as well. Long time project. Maybe for Octave 8 (or later).
 +
** See: [https://octave.discourse.group/t/1821 Windows, UTF-8, and UCRT - yet another variant of Octave on Windows?]
 +
 
 +
=== [https://en.wikipedia.org/wiki/Bus_factor Bus factor] ===
 +
 
 +
* Octave needs more documentation of release tasks.
 +
** E.g. https://octave.discourse.group/t/how-to-update-the-gui-translation-files/1834
 +
* jwe updates [[Project Infrastructure]] page.
 +
* Start an Octave Discourse thread about ideas how to ensure project continuity.
 +
 
 +
=== Octave 8 ideas ===
 +
 
 +
* jwe updated [[:Category:Development#jwe_priorities]] and clean up outdated [[JWE Project Ideas]].
 +
** @jwe: shall I (Kai) merge and redirect [[JWE Project Ideas]] into the general [[Projects]] page??
 +
* jwe wants to work on argument-list syntax.
 +
* rik wants to consistently use <code>OCTAVE_LOCAL_BUFFER</code> 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 <code>std:shared_ptr</code>? But they aren't guaranteed to be thread-safe by design either.
 +
** Eliminate <code>mutable</code> class data.
 +
* Other performance improvements:
 +
** Idea: memory pools: bug {{bug|57321}}
 +
** Idea: static_cast vs. dynamic_cast: patch {{patch|10139}}
 +
** General remark: Prefer standard features instead of "reinventing the wheel" by implementing intricate optimizations.
    
== See also ==
 
== See also ==
162

edits

Navigation menu