182
edits
Online Developer Meeting (2023-11-28): Difference between revisions
Online Developer Meeting (2023-11-28) (view source)
Revision as of 02:27, 29 November 2023
, 29 November 2023→Today's topics
m (→Today's topics) |
ArunGiridhar (talk | contribs) Tags: Mobile edit Mobile web edit |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
* Octave 9 release activities | * Octave 9 release activities | ||
** [[9.1 Release Checklist]] | ** [[9.1 Release Checklist]] | ||
** '''Continuing progress with language checks and translations''' | |||
* Consider reverting the removal of the configure flag that allows disabling the bytecode VM? | * Consider reverting the removal of the configure flag that allows disabling the bytecode VM? | ||
** Background discussion: https://octave.discourse.group/t/the-role-of-the-disable-vm-evaluator-flag/4934 | |||
** '''JWE will try to add ifdefs for this''' | |||
** '''It was discussed to make this activity as a bug report to help tracking''' | |||
* Clarify changes that should target the stable or the default branch. | * Clarify changes that should target the stable or the default branch. | ||
** '''No universal guidelines, generally ask whether it absolutely needs to be in stable without introducing new problems''' | |||
** Importance of impact, if any: does it make a difference whether it addresses a crash vs addresses something minor? | |||
** Importance of frequency, if any: does it make a difference whether the bug is commonly encountered or rare? | |||
** Size of code change, if any. | |||
** When to graft changes from default to stable? | |||
* Clarify what should be part of reviewing a change before pushing it to the repository. Any difference for changes to the stable or the default branch? | * Clarify what should be part of reviewing a change before pushing it to the repository. Any difference for changes to the stable or the default branch? | ||
** '''No all-use guidelines, but avoid compiler specific code, platform specific code, and in general ask why something is written this way''' | |||
* Decide on criteria for which bugs should be fixed before 9.1.0 release | * Decide on criteria for which bugs should be fixed before 9.1.0 release | ||
** Tag all bugs which meet criteria with Planned Release of 9.1.0 | ** Tag all bugs which meet criteria with Planned Release of 9.1.0 | ||
* Default to Qt6 for Octave 9? Also for MXE Octave? That raises minimum requirements for compiler (C++17) and target platform (for Windows: minimum Windows 10 64-bit, see [https://octave.discourse.group/t/transition-octave-to-qt6/3139/5 post on discourse]). | |||
* Enable polymorphic allocators by default (C++17 feature)? Might prevent Octave packages from building if they set a lower C++ standard. (Known example: the ltfat package does this currently, adding -std=gnu++11 to its flags, preventing it from being built as-is with polymorphic allocators.) | |||
== Previous topics == | == Previous topics == | ||