How to Release 5.8

From OTBWiki
Jump to: navigation, search

This article describes generic steps to perform release 5.8 (adapted from template How to release).

To take actions add your name (in bold) at the end of an item:

  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 5.8 RC1

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

Release 5.8

  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 (Guillaume)
  6. Sanity check the binary packages (2nd check on 8/11/16, Guillaume & Rashad)
    1. Linux : OK
    2. Windows 32bits : OK
  7. Tag the release branches (Guillaume)
  8. Merge the release into master (Guillaume)
  9. Prepare and upload source packages (Guillaume)
  10. Promote nightly packages (Guillaume)
  11. Update documentation (Guillaume)
  12. Upload OTB source archive to Zenodo to create a unique Digital Object Identifier (DOI) (Guillaume)
  13. Update the website "Home" and "Download" pages with version numbers and links. (Guillaume)
  14. Update OTB-Data-Examples.tgz on orfeo-toolbox (packages) (Guillaume)
  15. Send email to mailing list to announce the release (Manuel)
  16. Release announcement on the blog(Manuel)
  17. Announcement on social networks (twitter, google+)(Manuel)
  18. Plan the next release (nominate new release manager, setup PSC meeting on IRC)(Manuel)
  19. Contact QGis processing plugin maintainer to update XML description for new OTB-Applications (or supply it) (Manuel)