1,174
edits
10.1 Release Checklist: Difference between revisions
m
no edit summary
m (Mark items done) |
mNo edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
* 2025-02-07 🚀 Release Kick-off ⚽ (default branch merged to stable) | * 2025-02-07 🚀 Release Kick-off ⚽ (default branch merged to stable) | ||
* 2025-03-15 🛠️ 1st release candidate '''10.0.90''' on https://alpha.gnu.org/gnu/octave/ | * 2025-03-15 🛠️ 1st release candidate '''10.0.90''' on https://alpha.gnu.org/gnu/octave/ | ||
* 2025- | * 2025-03-28 🏁 Final Release 🎉 '''10.1.0''' on https://ftp.gnu.org/gnu/octave/}} | ||
Please use <code><strike> </strike></code> to mark items below as done. | Please use <code><strike> </strike></code> to mark items below as done. | ||
| Line 23: | Line 23: | ||
<strike> '''Must occur first''' as it could resolve existing, or create new, bug reports. The simple update command is <code>gnulib-tool --add-import</code> followed by running <code>./bootstrap</code> in the source tree. </strike> | <strike> '''Must occur first''' as it could resolve existing, or create new, bug reports. The simple update command is <code>gnulib-tool --add-import</code> followed by running <code>./bootstrap</code> in the source tree. </strike> | ||
=== ⚙️ <strike> Update Autoconf macros to latest version </strike> === | |||
Completion Date: 2025-03-23 | |||
<strike> The following Autoconf macros are under version control in the <code>m4</code> directory. The contents should be verified against the repository at https://github.com/autoconf-archive/autoconf-archive/tree/master/m4. | |||
ax_blas.m4 | |||
ax_compare_version.m4 | |||
ax_cxx_compile_stdcxx.m4 | |||
ax_lapack.m4 | |||
ax_openmp.m4 | |||
ax_pthread.m4 | |||
The <code>pkg.m4</code> macro should be verified against the repository at https://github.com/pkgconf/pkgconf/blob/master/pkg.m4. </strike> | |||
=== 📢 <strike> Call for bug reports </strike> === | === 📢 <strike> Call for bug reports </strike> === | ||
| Line 88: | Line 103: | ||
Completion Date of first iteration: | Completion Date of first iteration: 2025-03-06 | ||
=== ⚠️ Current state at Savannah === | === ⚠️ Current state at Savannah === | ||
| Line 124: | Line 139: | ||
Completion Date: | Completion Date: | ||
* Ensure correct version information in <code>configure.ac</code> (see “Release Numbering” in <code>/etc/HACKING.md</code>) | * <strike> Ensure correct version information in <code>configure.ac</code> (see “Release Numbering” in <code>/etc/HACKING.md</code>) | ||
** Set <code>OCTAVE_RELEASE_DATE</code> to the current date. | ** Set <code>OCTAVE_RELEASE_DATE</code> to the current date. | ||
** Set the year in <code>OCTAVE_COPYRIGHT</code> to the current year. | ** Set the year in <code>OCTAVE_COPYRIGHT</code> to the current year. | ||
| Line 130: | Line 145: | ||
* Update <code>etc/NEWS.10.md</code> (final release date in Summary header). | * Update <code>etc/NEWS.10.md</code> (final release date in Summary header). | ||
* Update <code>CITATION</code> (version, year, URL) if not already done as part of "GPL License activities. | * Update <code>CITATION</code> (version, year, URL) if not already done as part of "GPL License activities. | ||
* Update <code>etc/icons/org.octave.Octave.appdata.xml</code> (version number and release date). | * Update <code>etc/icons/org.octave.Octave.appdata.xml</code> (version number and release date). </strike> | ||
* Upload all tarballs to https://ftp.gnu.org/gnu/octave/. | * Upload all tarballs to https://ftp.gnu.org/gnu/octave/. | ||
* Update web site files: <code>NEWS-10.html</code>, <code>index.in</code>, <code>news.in</code>, and <code>download.in</code>. | * Update web site files: <code>NEWS-10.html</code>, <code>index.in</code>, <code>news.in</code>, and <code>download.in</code>. | ||
* Update https://wiki.octave.org/Release_History page. | * <strike> Update https://wiki.octave.org/Release_History page. | ||
* Update Savannah bug tracker <code>Release</code> field to have new release number. | * Update Savannah bug tracker <code>Release</code> field to have new release number. | ||
* Update Savannah bug tracker: '''OPEN''' bugs marked as '''WON’T FIX''' should be marked as '''CONFIRMED''' (or more appropriate) for the final release. | * Update Savannah bug tracker: '''OPEN''' bugs marked as '''WON’T FIX''' should be marked as '''CONFIRMED''' (or more appropriate) for the final release. | ||
* Hide release candidate versions for <code>Release</code> field on Savannah. | * Hide release candidate versions for <code>Release</code> field on Savannah. </strike> | ||
=== 📢 Announce final release === | === 📢 Announce final release === | ||