Editing 9.1 Release Checklist

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{Note|'''Timeline''' (tentative)
{{Note|'''Timeline''' (tentative)
* 2023-11-22 πŸš€ Release Kick-off ⚽ (default branch merged to stable)
* 2023-11-22 πŸš€ Release Kick-off ⚽ (default branch merged to stable)
* 2024-02-07 πŸ› οΈ 1st release candidate '''9.0.90''' on https://alpha.gnu.org/gnu/octave/
* 2023-12-xx πŸ› οΈ 1st release candidate '''9.0.90''' on https://alpha.gnu.org/gnu/octave/
* 2024-03-14 🏁 Final Release πŸŽ‰ '''9.1.0''' on https://ftp.gnu.org/gnu/octave/}}
* 2023-12-xx 🏁 Final Release πŸŽ‰ '''9.1.0''' on https://ftp.gnu.org/gnu/octave/}}


:Please use <code>&lt;strike&gt; &lt;/strike&gt;</code> to mark items below as done.
:Please use <code>&lt;strike&gt; &lt;/strike&gt;</code> to mark items below as done.
Line 16: Line 16:


=== πŸ“’ Update GUI translation files ===
=== πŸ“’ Update GUI translation files ===
:Completion Date: 2023-12-22
:Completion Date: Β 
* <strike> Call for updates that might change GUI strings. </strike>
* <strike> Call for updates that might change GUI strings. </strike>
* String freeze date: 2023-12-03
* String freeze date: 2023-12-03
Line 22: Line 22:
* <strike> Create issue report on Savannah as a centralized location for uploading files. bug {{bug|64982}} </strike>
* <strike> Create issue report on Savannah as a centralized location for uploading files. bug {{bug|64982}} </strike>
* <strike> Call for translations for GUI strings on maintainers@octave.org, CC-ing the translators (see [https://hg.savannah.gnu.org/hgweb/octave/file/tip/libgui/languages/translators list of translators]). [https://lists.gnu.org/archive/html/octave-maintainers/2023-11/msg00004.html message in mailing list archive] </strike>
* <strike> Call for translations for GUI strings on maintainers@octave.org, CC-ing the translators (see [https://hg.savannah.gnu.org/hgweb/octave/file/tip/libgui/languages/translators list of translators]). [https://lists.gnu.org/archive/html/octave-maintainers/2023-11/msg00004.html message in mailing list archive] </strike>
* <strike> Collect and push all translated files. </strike>
* Collect and push all translated files.


=== <strike> βš™οΈ Update gnulib to latest version </strike> ===
=== <strike> βš™οΈ Update gnulib to latest version </strike> ===
Line 30: Line 30:
=== βš–οΈ GPL License activities ===
=== βš–οΈ GPL License activities ===
:Completion Date: Β 
:Completion Date: Β 
* <strike> Update copyright statements for all source controlled files. </strike>
* Update copyright statements for all source controlled files. Β 
* Update dates in any other locations (launch message, <strike> CITATION </strike>, MXE files, etc.). Β 
* Update dates in any other locations (launch message, citation, MXE files, etc.). Β 
* <strike> Add any new contributors to {{Path|doc/interpreter/contributors.in}} who wish to be mentioned (don't add them without permission). </strike>
* Add any new contributors to {{Path|doc/interpreter/contributors.in}} who wish to be mentioned (don't add them without permission).


=== βœ… Style-check code base ===
=== βœ… Style-check code base ===
:Completion Date: 2023-12-12
:Completion Date: 2023-12-12
: <strike> This will produce lots of whitespace changes, but no behavior changes. '''Must occur after patches have been added''', since whitespace changes can prevent patches from applying. </strike>
: This will produce lots of whitespace changes, but no behavior changes. '''Must occur after patches have been added''', since whitespace changes can prevent patches from applying. Β 
* <strike> [[Octave style guide|m-file style check]] </strike>
* <strike> [[Octave style guide|m-file style check]] </strike>
* <strike> [[C++ style guide|C++ style check]] </strike>
* <strike> [[C++ style guide|C++ style check]] </strike>
Line 60: Line 60:
=== βœ… <code>make check</code> ===
=== βœ… <code>make check</code> ===
* Verify <code>make check</code> is passing on all [http://buildbot.octave.org:8010/#/waterfall buildbot combinations of OS and compilers] and [https://github.com/gnu-octave/octave/actions GitHub CI runners]. Also check [https://github.com/gnu-octave/octave-buildbot/actions test suite runs on "freshly brewed Octave for Windows"] (Kai's buildbots on octave.space).
* Verify <code>make check</code> is passing on all [http://buildbot.octave.org:8010/#/waterfall buildbot combinations of OS and compilers] and [https://github.com/gnu-octave/octave/actions GitHub CI runners]. Also check [https://github.com/gnu-octave/octave-buildbot/actions test suite runs on "freshly brewed Octave for Windows"] (Kai's buildbots on octave.space).
* <strike> Compiling with <code>-fsanitize=undefined</code>, <code>--enable-address-sanitizer-flags</code> to check for memory leaks. Use other tools <code>cppcheck</code>, etc. </strike>
* Compiling with <code>-fsanitize=undefined</code>, <code>--enable-address-sanitizer-flags</code> to check for memory leaks. Use other tools <code>cppcheck</code>, etc. Β 
** <strike> Update PVS static analyzer results [[PVS static analyzer - 5.0 Release]]. </strike> WON'T DO
** Update PVS static analyzer results [[PVS static analyzer - 5.0 Release]].
** <strike> Or use any static analyzer, such as Clang's `scan-build make all`. </strike> WON'T DO
** Or use any static analyzer, such as Clang's `scan-build make all`.
* Start discussion on Discourse about which failing tests that must be fixed and which can be declared '''WON'T FIX''': [https://octave.discourse.group/t/test-suite-results-of-octave-9/5077 Test suite results of Octave 9]
* Start discussion on maintainers@octave.org about which failing tests that must be fixed and which can be declared '''WON'T FIX'''.


=== πŸ› οΈ Create new release candidate ===
=== πŸ› οΈ Create new release candidate ===
Line 92: Line 92:
:Completion Date:
:Completion Date:
* Octave mailing-lists
* Octave mailing-lists
* <strike>Octave web site (https://github.com/gnu-octave/gnu-octave.github.io)</strike>
* Octave web site (https://hg.octave.org/web-octave)
** <strike>Steps documented in [https://github.com/gnu-octave/gnu-octave.github.io/commit/b623a44ffebfc610402caa5318bc44f5e2c8a52d this changeset].</strike>
** Steps documented in [https://hg.octave.org/web-octave/rev/fe59d0118a2b this changeset].
** <strike>Upload documentation (manual HTML + PDF {{Path|octave.org/doc}} and version in {{Path|octave.org/.htaccess}}, Doxygen {{Path|octave.org/doxygen}})</strike>
** Upload documentation (manual HTML + PDF {{Path|octave.org/doc}} and version in {{Path|octave.org/.htaccess}}, Doxygen {{Path|octave.org/doxygen}})
* <strike>This wiki</strike>
* This wiki
** [[Template:Release]] = {{Release}}
** [[Template:Release]] = {{Release}}
** [[Template:Release Date]] = {{Release Date}}
** [[Template:Release Date]] = {{Release Date}}
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)