11.1 Release Checklist: Difference between revisions

Jump to navigation Jump to search
m
Line 140: Line 140:
Completion Date:
Completion Date:


* Ensure correct version information in <code>configure.ac</code> (see β€œRelease Numbering” in <code>/etc/HACKING.md</code>)
* Ensure correct version information in <code>configure.ac</code> (see β€œRelease Numbering” in <code>etc/HACKING.md</code>)
** Update <code>AC_INIT</code> macro wi/th version <code>MAJOR.MINOR.PATCH</code>.
** Update <code>AC_INIT</code> macro with version <code>MAJOR.MINOR.PATCH</code>.
** Set <code>OCTAVE_MINOR_VERSION</code> to version <code>MINOR</code>.
** Set <code>OCTAVE_MINOR_VERSION</code> to version <code>MINOR</code>.
** Set <code>OCTAVE_PATCH_VERSION</code> to version <code>PATCH</code>.
** Set <code>OCTAVE_PATCH_VERSION</code> to version <code>PATCH</code>.
Line 149: Line 149:
* Update <code>CITATION</code> (version, year, URL) if not already done as part of &quot;GPL License activities&quot;.
* Update <code>CITATION</code> (version, year, URL) if not already done as part of &quot;GPL License activities&quot;.
* Update <code>etc/icons/org.octave.Octave.appdata.xml</code> (Add <code><release></code> with release date and version number).
* Update <code>etc/icons/org.octave.Octave.appdata.xml</code> (Add <code><release></code> with release date and version number).
=== πŸ“ƒ Build, Verify, Sign, and Upload tarballs and Windows binaries ===
* Make distribution tarballs and Windows binaries
* Make distribution tarballs and Windows binaries
** Run <code>make dist</code> on Linux to produce distribution tarballs.
** Run <code>make dist</code> on Linux to produce distribution tarballs.
** Make Windows binaries
** Make Windows binaries (see instructions in <code>etc/HACKING.md</code>).
::'''DETAILED INSTRUCTIONS NEEDED'''
* Verify building from a tarball on Linux.  Verify that Windows binaries install and run.
* Verify building from a tarball on Linux and verify that Windows binaries install and run.
* Create a tag in the Mercurial repository on the changeset where the version number was updated (<code>hg tag release-VERSION-1-0</code>).
* Create <code>hg tag</code> in repository with release candidate version number (<code>release-VERSION-1-0</code>).
* Sign tarballs and binaries with GPG key.
** Use script <code>build-aux/make-gnu-fist-files</code> to simplify the procedure.
* Upload all tarballs to https://ftp.gnu.org/gnu/octave/.
* Upload all tarballs to https://ftp.gnu.org/gnu/octave/.


 
=== πŸ“ƒ Update Octave web site, Octave wiki, and Savannah bug tracker ===


* Update web site files: <code>NEWS-VERSION.html</code>, <code>index.in</code>, <code>news.in</code>, and <code>download.in</code>.
* Update web site files: <code>NEWS-VERSION.html</code>, <code>index.in</code>, <code>news.in</code>, and <code>download.in</code>.
* Update https://wiki.octave.org/Release_History page.
:Steps documented in this [https://hg.octave.org/web-octave/rev/fe59d0118a2b changeset].
* Upload documentation (manual HTML + PDF at <code>octave.org/doc</code>, version in <code>octave.org/.htaccess</code>, Doxygen at <code>octave.org/doxygen</code>)
* 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.
* Update Octave [[GNU_Octave_Wiki|wiki]]
** Update https://wiki.octave.org/Release_History page.
** Edit page [[Template:Release]] and update release version in code <pre><includeonly>MAJOR.MINOR.PATCH</includeonly></pre>
** Edit page [[Template:Release Date]] and update month and day in code <pre><includeonly>MONTH DD, {{Release Year}}</includeonly></pre>
** Edit page [[Template:Release Year]] and update year in code <pre><includeonly>YYYY</includeonly></pre>


=== πŸ“’ Announce final release ===
=== πŸ“’ Announce final release ===
Line 171: Line 181:
* Octave mailing-lists (yes, still) [mailto:help@octave.org help@octave.org] and [mailto:info-gnu@gnu.org info-gnu@gnu.org].
* Octave mailing-lists (yes, still) [mailto:help@octave.org help@octave.org] and [mailto:info-gnu@gnu.org info-gnu@gnu.org].
* Octave web site (https://hg.octave.org/web-octave)
* Octave web site (https://hg.octave.org/web-octave)
* Steps documented in this [https://hg.octave.org/web-octave/rev/fe59d0118a2b changeset].
 
* Upload documentation (manual HTML + PDF <code>octave.org/doc</code> and version in <code>octave.org/.htaccess</code>, Doxygen <code>octave.org/doxygen</code>)
* Update Octave [[GNU_Octave_Wiki|wiki]]
** Edit page [[Template:Release]] and update release version in code <pre><includeonly>MAJOR.MINOR.PATCH</includeonly></pre>
** Edit page [[Template:Release Date]] and update month and day in code <pre><includeonly>MONTH DD, {{Release Year}}</includeonly></pre>
** Edit page [[Template:Release Year]] and update year in code <pre><includeonly>YYYY</includeonly></pre>


=== β˜‘οΈ Post-Release ===
=== β˜‘οΈ Post-Release ===
1,173

edits

Navigation menu