How to Release 5.8

From OTBWiki
Revision as of 13:20, 7 October 2016 by Manuel.grizonnet (Talk | contribs) (Created page with "This article describes generic steps to perform release 5.8. Adapted from template. To take actions change: # Send an email to otb-developers to announce the beginning of the...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This article describes generic steps to perform release 5.8. Adapted from template.

To take actions change:

  1. Send an email to otb-developers to announce the beginning of the release process.

to

  1. Send an email to otb-developers to announce the beginning of the release process (John Doe)

When the action is completed, you cross out the item: # Send an email to otb-developers to announce the beginning of the release process (John Doe)




[Major Release] Feature Freeze and RC1

  1. Create the new release branch
  2. Send an email to otb-developers to announce the beginning of the release process.
  3. run debian spelling checker
  4. Update version numbers (in develop) to a development version.
  5. Update version numbers (in release-X.Y) in CMakeLists.txt for OTB (and optionally Monteverdi).
  6. Update FAQ, Cookbook and Software Guide (download, installation and compilation sections, contributor list) in both develop and release branch.
  7. Update dashboard scripts to support new version numbers
  8. Update release notes with mantis bug report and improvements for OTB, Monteverdi and Ice (walk the git history, RFCs & co.)
  9. Update the SuperBuild archive
  10. Add new remote modules candidates that can be added to Modules/Remote (should be previously discussed on otb mailing lists)
  11. Update GIT_TAG for all official remote modules
  12. Sanity check the binary packages
  13. Tag the release branches
  14. Prepare and upload source packages
  15. Promote nightly packages
  16. Update documentation
  17. Send RC announcement email (including updated checkout commands).
  18. Post RC announcement on the blog

Release

  1. [Minor Release only] Version number update in source code (branch release-X.Y)
  2. [Minor Release only] SuperBuild archive update (if needed)
  3. Update release notes with mantis bug report and improvements.
  4. Update release notes (walk the git history and log all improvements) for OTB, Monteverdi and Ice.
  5. Update the date in RELEASE_NOTES.txt
  6. Sanity check the binary packages
  7. Tag the release branches
  8. Merge the release into master
  9. Prepare and upload source packages
  10. Promote nightly packages
  11. Update documentation
  12. Upload OTB source archive to Zenodo to create a unique Digital Object Identifier (DOI)
  13. Update the website "Home" and "Download" pages with version numbers and links.
  14. Update OTB-Data-Examples.tgz on orfeo-toolbox (packages)
  15. Send email to mailing list to announce the release
  16. Release announcement on the blog
  17. Announcement on social networks (twitter, google+)
  18. Plan the next release (nominate new release manager, setup PSC meeting on IRC)
  19. Contact QGis processing plugin maintainer to update XML description for new OTB-Applications (or supply it)