OTB 10 Release
We are ready to release OTB version 10.0.0. The following steps need to be done:
Release Candidate
1. Branches
-
(if major or minor release) Feature freeze: create the new release branch -
(if patch release) Work on the already existing branch release-MAJOR-MINOR -
Make sure the version number in CMakeLists.txtis 10.0.0
2. Housekeeping
-
In this story, make a list of blocking issues for the release (if any) -
Update release notes (walk the GitLab MR merged history and log all improvements) -
Update the date in RELEASE_NOTES.txt -
Check SonarQube -
Run Debian spelling checker -
Run shellcheck script from OTB-Devutils/Scripts/ -
Sanity check the binary packages -
Windows -
Linux -
QGIS plugin
-
3. Actual release candidate
Once all blocking issues are closed, and the previous steps are done:
-
Tag the release candidate -
Update GIT_TAG for all official remote modules (if needed)
4. Publish and plan next release
-
Prepare and upload source packages -
Promote staging packages -
Update documentation -
Cookbook. If it is a patch version, overwrite in version.html file the previous minor version to only keep one minor version. This will be updated when merged in develop. -
Doxygen
-
-
Update the SuperBuild archive -
Release Candidate announcement on the forum -
Add the new release to TRex Help for release actions
Release
1. Branches
-
Make sure the version number in CMakeLists.txtis MAJOR.MINOR.PATCH
2. Housekeeping
-
In this story, make a list of blocking issues for the release (if any) -
Fix compilation warnings on CI -
Update release notes (walk the GitLab MR merged history and log all improvements) -
Update the date in RELEASE_NOTES.txt -
Check SonarQube -
Run Debian spelling checker -
Run shellcheck script from OTB-Devutils/Scripts/ -
Sanity check the binary packages -
Windows -
Linux -
QGIS plugin
-
3. Actual release
Once all blocking issues are closed, and the previous steps are done:
-
Tag the release -
(if major or minor release): Merge the release into develop -
(if it's the latest release): Merge the release into master -
(if patch release): Backport fixes -
Update GIT_TAG for all official remote modules (if needed)
4. Publish and plan next release
-
Prepare and upload source packages -
Promote staging packages -
Update documentation -
Cookbook -
Doxygen -
WordPress page "Home" and "Download" pages
-
-
Add the release to "Releases" page of the project -
Update the SuperBuild archive -
Upload OTB source archive to Zenodo to create a unique Digital Object Identifier (DOI) -
Release announcement -
Update the Wikipedia page with the version number and release date (https://en.wikipedia.org/wiki/Orfeo_toolbox) -
Forward announcement to news_item@osgeo.org (OSGeo news) -
Remove public branches related to MR or bugfix merged before the release -
Add the new release to TRex Help for release actions
Edited by Tristan Laurent