Difference between revisions of "6.3 Release Checklist"

From Octave
Jump to navigation Jump to search
m (Mark items done)
m (Clarify update to NEWS file)
Line 24: Line 24:
 
* <strike> Spell check documentation. </strike>
 
* <strike> Spell check documentation. </strike>
 
* <strike> Verify all formats (Info, HTML, PDF) build correctly. </strike>
 
* <strike> Verify all formats (Info, HTML, PDF) build correctly. </strike>
* Review {{Path|NEWS}} for any features which should be announced.
+
* For minor release, review Mercurial logs for any bugs fixed on stable and publish in {{Path|NEWS}} file
  
 
=== <strike> Translations </strike> ===
 
=== <strike> Translations </strike> ===

Revision as of 14:28, 17 May 2021

Info icon.svg
Timeline (tentative)
Please use <strike> </strike> to mark items below as done.

Kick-off

Updates for gnulib

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

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.

  • Grammar check documentation.
  • Spell check documentation.
  • Verify all formats (Info, HTML, PDF) build correctly.
  • For minor release, review Mercurial logs for any bugs fixed on stable and publish in NEWS file

Translations

We don't normally update translation files for bug-fixing releases.

make check

  • Verify make check is passing on all buildbot combinations of OS and compilers.
  • Compiling with -fsanitize=undefined, --enable-address-sanitizer-flags to check for memory leaks. Use other tools cppcheck, etc.

Create new release candidate

  • Ensure correct version information.
  • Create hg tag in repository with release candidate version number.
  • Verify make distcheck passes.
  • Verify make dist 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 version information.
  • Create hg tag in repository with release version number.
  • Update NEWS (final release date).
  • Update CITATION (version, year, URL).
  • Update 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

Post-Release

  • Update version info in configure.ac on stable branch and merge with default version information.

Versioning hints

Info icon.svg
Read etc/HACKING.md carefully!!
  • Update configure.ac:
    • AC_INIT
    • OCTAVE_API_VERSION
    • OCTAVE_MAJOR/MINOR/PATCH_VERSION
    • OCTAVE_RELEASE_DATE
  • Update libtool versioning:
    • liboctave/module.mk %canon_reldir%_%canon_reldir%_current
    • libinterp/module.mk %canon_reldir%_liboctinterp_current
    • libgui/module.mk %canon_reldir%_liboctgui_current