The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
Release 7 planning
We are ready to release OTB version 7.0.0. The following steps need to be done:
- Wait for all isues marked 7.0.0 and feature to be merged
Release candidate
1. Branches
- (if major or minor release) Feature freeze: create the new release branch
-
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)
- #1969 (closed)
- #1930 (closed) (not blocking for the rc).
- Update the SuperBuild archive. Note: waiting for the actual release to move the 6.6.1 archive
- Update release notes (walk the GitLab MR merged history and log all improvements)
- Update the date in RELEASE_NOTES.txt
- Run Debian spelling checker
- Run shellcheck script from OTB-Devutils/Scripts/
- Update translation for Monteverdi and Mapla
-
Sanity check the binary packages
- Windows
- Linux
- Mac , ok but #1930 (closed) has been reproduced.
3. Actual release
Once all blocking issues are closed, and the previous steps are done:
- Tag the release or RC for the rc onldy otb tag has been create
- 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
- Release announcement on the forum
Announcement on social networks (twitter, google+)
Release
1. Branches
- (if major or minor release) Feature freeze: create the new release branch
-
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)
- #1969 (closed)
- #1930 (closed) (not blocking for the rc).
- Update the SuperBuild archive. Note: waiting for the actual release to move the 6.6.1 archive
- Update release notes (walk the GitLab MR merged history and log all improvements)
- Update the date in RELEASE_NOTES.txt
- Run Debian spelling checker
- Run shellcheck script from OTB-Devutils/Scripts/
- Update translation for Monteverdi and Mapla
-
Sanity check the binary packages
- Windows
- Linux
- Mac
3. Actual release
Once all blocking issues are closed, and the previous steps are done:
- Tag the release or RC for the rc onldy otb tag has been create
- Merge the release into develop
- Merge the release into master
- 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
- Upload OTB source archive to Zenodo to create a unique Digital Object Identifier (DOI)
- Release announcement on the forum
- Release announcement on the blog
- Announcement on social networks (twitter, google+)
- Forward announcement to news_item@osgeo.org (OSGeo news)
Plan the next release (nominate new release manager, setup PSC meeting on IRC)- Remove public branches related to MR or bugfix merged before the release