Online Developer Meeting (2023-11-28): Difference between revisions

→‎Today's topics: Added specific questions to help me
(→‎Today's topics: more topics)
(→‎Today's topics: Added specific questions to help me)
Tags: Mobile edit Mobile web edit
Line 7: Line 7:
** [[9.1 Release Checklist]]
** [[9.1 Release Checklist]]
* 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
* Clarify changes that should target the stable or the default branch.
* Clarify changes that should target the stable or the default branch.
** 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?
* 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]).
* 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.
* 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 ==
171

edits