7.1 Release Checklist: Difference between revisions
Jump to navigation
Jump to search
â
(âââī¸ Update gnulib to latest version: Add completion date) |
|||
Line 24: | Line 24: | ||
=== âī¸ Update gnulib to latest version === | === âī¸ Update gnulib to latest version === | ||
:Completion Date: | :Completion Date: 2021-11-18 | ||
:Must occur first as it could resolve existing, or create new, bug reports. You should run <code>./bootstrap</code> in the source tree after updating to the new gnulib version. | :Must occur first as it could resolve existing, or create new, bug reports. You should run <code>./bootstrap</code> in the source tree after updating to the new gnulib version. | ||
Revision as of 19:14, 24 November 2021
Timeline (tentative)
- 2021-11-yy đ Release Kick-off âŊ (default branch not yet merged to stable!)
- 2022-xx-yy đ ī¸ First Release candidate 7.0.90 on https://alpha.gnu.org/gnu/octave/
- ...
- 2022-xx-yy đ Final Release đ 7.1.0 on https://ftp.gnu.org/gnu/octave/
- Please use
<strike> </strike>
to mark items below as done.
đ Kick-off âŊ
đĸ Call for bug reports
- Completion Date:
- Put out a general call for reports on Octave Discourse for all outstanding unreported known bugs.
- Create Savannah tag 7.0.90 on bug tracker.
- Mark items that should be fixed for the release with this tag.
- Bug overview at https://octave.space/savannah/ .
đĸ Call for translations
- Completion Date:
- Call for translations for GUI strings on Octave Discourse.
- Update language translation files (*.ts).
- Create issue report on Savannah as a centralized location for uploading files.
- Collect and push all translated files.
âī¸ Update gnulib to latest version
- Completion Date: 2021-11-18
- Must occur first as it could resolve existing, or create new, bug reports. You should run
./bootstrap
in the source tree after updating to the new gnulib version.
âī¸ GPL License activities
- Completion Date:
- Update copyright statements for all source controlled files.
- Update dates in any other locations (launch message, citation, MXE files, etc.).
- Add any new contributors to doc/interpreter/contributors.in who wish to be mentioned (don't add them without permission).
â Style-check code base
- Completion Date:
- 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.
đ Review documentation
- Completion Date:
- Grammar check documentation.
- Spell check documentation.
- Verify no functions missing from manual.
- Verify deprecated functions removed from "see also" links.
- Verify all formats (Info, HTML, PDF) build correctly.
- Review NEWS for any features which should be announced.
- Review __unimplemented__.m for the latest changes to Octave Forge packages and new Matlab functions.
- Update major version number in "@subtitle Edition XXX" in octave.texi.
- Update installer-files/README.html in MXE Octave with version highlights.
đ Repeat until all bugs are resolved
- Completion Date first iteration:
â ī¸ Current state at Savannah
- Bug overview at https://octave.space/savannah/ .
â
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 toolscppcheck
, etc.- Update PVS static analyzer results PVS static analyzer - 5.0 Release.
- 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
- 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 Octave Discourse.
đ Final Release đ
đ Update version information
- Completion Date:
- 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
- Completion Date:
- Octave mailing-lists
- Octave web site (https://hg.octave.org/web-octave)
- Steps documented in this changeset.
- Upload documentation (manual HTML + PDF octave.org/doc and version in octave.org/.htaccess, Doxygen octave.org/doxygen)
- This wiki
- Template:Release = 9.2.0
- Template:Release Date = June 1, 2024
- Template:Release Year = 2024
âī¸ Post-Release
- Completion Date:
- Merge default onto stable to become the current stable release.
- Ensure correct version information.
- Remove all deprecated functions (either
OCTAVE_DEPRECATED
in C++ or scripts/deprecated for m-files) scheduled for deletion in "default" branch. - Move NEWS file to backup in etc/NEWS.X.
- Create new NEWS file.
âšī¸ Versioning hints
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
- liboctave/module.mk