Editing 6.3 Release Checklist


{{Note|'''Timeline''' (tentative)
* 2021-05-11 Begin 6.3 Release Process
* 2021-05-18 First Release candidate '''6.2.9''' on https://alpha.gnu.org/gnu/octave/
* 2021-05-25 Final Release '''6.3.0''' on https://ftp.gnu.org/gnu/octave/}}

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

== Kick-off ==

=== <strike> Updates for gnulib </strike> ===

<strike>For bug-fixing releases, changes to gnulib should only be done to fix known serious problems.  There were none for 6.3.</strike>

=== Bugs that should be fixed before the release ===

: https://octave.space/savannah/?Action=get&Format=HTMLCSS&ItemID=56952,57557,59735,60209,59729,60174,60531,60471,60470

=== Review documentation ===

The following is all we should need to do for a minor release.

* <strike> Grammar check documentation. </strike>
* <strike> Spell check documentation. </strike>
* <strike> Verify all formats (Info, HTML, PDF) build correctly. </strike>
* <strike>For minor release, review Mercurial logs for any bugs fixed on stable and publish in {{Path|NEWS}} file</strike>
* <strike>Update installer {{Path|README.html}} file in MXE Octave.</strike>

=== <strike> Translations </strike> ===

<strike>We don't normally update translation files for bug-fixing releases.</strike>

=== <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].
* Compiling with <code>-fsanitize=undefined</code>, <code>--enable-address-sanitizer-flags</code> to check for memory leaks. Use other tools <code>cppcheck</code>, etc. 

=== Create new release candidate ===

* Ensure correct [[#Versioning hints|version information]].
* Create hg tag in repository with release candidate version number.
* Verify <code>make distcheck</code> passes.
* Verify <code>make dist</code> works.
* Create [[Windows Installer]].
* Upload release candidates.
* Add release candidate version to Savannah bug tracker.
* Announce release candidate to discourse.

== Final Release ==

=== Update version information ===

* Ensure correct [[#Versioning hints|version information]].
* Create hg tag in repository with release version number.
* Update {{Path|NEWS}} (final release date).
* Update {{Path|CITATION}} (version, year, URL).
* Update {{Path|org.octave.Octave.appdata.xml}} (version number and release date).
* Update Savannah bug tracker version info.
* Update Savannah bug tracker: '''OPEN''' bugs marked as '''WON'T FIX''' should be marked as '''CONFIRMED''' (or more appropriate) for the final release.
* Remove release candidate versions from Savannah.

=== Announce final release ===

* Octave mailing-lists
* Octave web site (https://hg.octave.org/web-octave)
** Steps documented in [https://hg.octave.org/web-octave/rev/fe59d0118a2b this changeset].
** Upload documentation (manual HTML + PDF {{Path|octave.org/doc}} and version in {{Path|octave.org/.htaccess}}, Doxygen {{Path|octave.org/doxygen}}, NEWS)
* This wiki
** [[Template:Release]] = {{Release}}
** [[Template:Release Date]] = {{Release Date}}
** [[Template:Release Year]] = {{Release Year}}

== Post-Release ==

* Update version info in configure.ac on stable branch and merge with default [[#Versioning hints|version information]].

== Versioning hints ==

{{Note|Read [https://hg.savannah.gnu.org/hgweb/octave/file/tip/etc/HACKING.md <code>etc/HACKING.md</code>] carefully!!}}

* Update {{Path|configure.ac}}:
** <code>AC_INIT</code>
** <code>OCTAVE_API_VERSION</code>
** <code>OCTAVE_MAJOR/MINOR/PATCH_VERSION</code>
** <code>OCTAVE_RELEASE_DATE</code>
* Update libtool versioning:
** {{Path|liboctave/module.mk}} <code>%canon_reldir%_%canon_reldir%_current</code>
** {{Path|libinterp/module.mk}} <code>%canon_reldir%_liboctinterp_current</code>
** {{Path|libgui/module.mk}} <code>%canon_reldir%_liboctgui_current</code>

[[Category:Releases]]