10.1 Release Checklist: Difference between revisions

m
Update version numbers
(Create new page)
 
m (Update version numbers)
Line 1: Line 1:
# `VERSION`.1 Release Checklist #
# 10.1 Release Checklist #


**Timeline** (tentative)
**Timeline** (tentative)


* YYYY-MM-DD 🚀 Release Kick-off ⚽ (default branch merged to stable)
* YYYY-MM-DD 🚀 Release Kick-off ⚽ (default branch merged to stable)
* YYYY-MM-DD 🛠️ 1st release candidate **`VERSION`.0.90** on
* YYYY-MM-DD 🛠️ 1st release candidate **10.0.90** on
   <https://alpha.gnu.org/gnu/octave/>
   <https://alpha.gnu.org/gnu/octave/>
* YYYY-MM-DD 🏁 Final Release 🎉 **`VERSION`.1.0** on
* YYYY-MM-DD 🏁 Final Release 🎉 **10.1.0** on
   <https://ftp.gnu.org/gnu/octave/>
   <https://ftp.gnu.org/gnu/octave/>


Line 25: Line 25:
* Bump version numbers in `configure.ac` on default branch (see
* Bump version numbers in `configure.ac` on default branch (see
   `etc/HACKING.md`).
   `etc/HACKING.md`).
* Create new `etc/NEWS.VERSION+1.md` file on default branch by copying
* Create new `etc/NEWS.11.md` file on default branch by copying
   `etc/NEWS.VERSION.md` and then removing text so that it is a template file
   `etc/NEWS.10.md` and then removing text so that it is a template file
   with headings only.
   with headings only.


Line 42: Line 42:


* Put out a general call for reports on [Octave Discourse](https://octave.discourse.group/) for all outstanding, but unreported, known bugs.
* Put out a general call for reports on [Octave Discourse](https://octave.discourse.group/) for all outstanding, but unreported, known bugs.
* Create Savannah `Release` tag `VERSION.0.90` on bug tracker for 1st release
* Create Savannah `Release` tag `10.0.90` on bug tracker for 1st release
   candidate.
   candidate.
* Mark items that should be fixed for the release with this tag.
* Mark items that should be fixed for the release with this tag.
* Update Savannah `Planned Release` and `Fixed Release` tags by adding
* Update Savannah `Planned Release` and `Fixed Release` tags by adding
   `VERSION.1.0 (current stable)` and `VERSION+1.1.0 (current default)`.
   `10.1.0 (current stable)` and `11.1.0 (current default)`.
* Review bug overview at <https://octave.space/savannah/>.
* Review bug overview at <https://octave.space/savannah/>.


Line 103: Line 103:
   links.
   links.
* Verify all formats (Info, HTML, PDF) build correctly.
* Verify all formats (Info, HTML, PDF) build correctly.
* Review `etc/NEWS.VERSION.md` for any features which should be announced.
* Review `etc/NEWS.10.md` for any features which should be announced.
* Review `__unimplemented__.m` for the latest changes to
* Review `__unimplemented__.m` for the latest changes to
   [Octave Forge](https://wiki.octave.org/Octave_Forge) packages and new Matlab
   [Octave Forge](https://wiki.octave.org/Octave_Forge) packages and new Matlab
Line 166: Line 166:
   * Set the year in `OCTAVE_COPYRIGHT` to the current year.
   * Set the year in `OCTAVE_COPYRIGHT` to the current year.
* Create `hg tag` in repository with release candidate version number
* Create `hg tag` in repository with release candidate version number
   (`release-VERSION-1-0`).
   (`release-10-1-0`).
* Update `etc/NEWS.VERSION.md` (final release date in Summary header).
* Update `etc/NEWS.10.md` (final release date in Summary header).
* Update `CITATION` (version, year, URL) if not already done as part of "GPL
* Update `CITATION` (version, year, URL) if not already done as part of "GPL
   License activities.
   License activities.
Line 173: Line 173:
   date).
   date).
* Upload all tarballs to <https://ftp.gnu.org/gnu/octave/>.
* Upload all tarballs to <https://ftp.gnu.org/gnu/octave/>.
* Update web site files: `NEWS-VERSION.html`, `index.in`, `news.in`, and
* Update web site files: `NEWS-10.html`, `index.in`, `news.in`, and
   `download.in`.
   `download.in`.
* Update <https://wiki.octave.org/Release_History> page.
* Update <https://wiki.octave.org/Release_History> page.
Line 203: Line 203:
   branch.  These functions are tagged with `OCTAVE_DEPRECATED` in C++ or are
   branch.  These functions are tagged with `OCTAVE_DEPRECATED` in C++ or are
   m-files located in the directory `scripts/deprecated`.  Check file
   m-files located in the directory `scripts/deprecated`.  Check file
   `etc/NEWS.VERSION-2.md` for list of features that have been deprecated.
   `etc/NEWS.8.md` for list of features that have been deprecated.
1,135

edits