How to Release 3.16

Release Candidate preparation

J-2

• Update version numbers in CMakeLists.txt
• Update version numbers in doxygen
• Update version numbers in software guide and cookbook
• Update release notes
  • Walk the mercurial history and log all improvements
  • Generate mantis report
    • Use Advanced Filters
    • Select all projects in the combobox : Orfeo Toolbox (OTB)
    • Set "Use Date" and "Resolution" filters
    • Export in cvs format
    • Use processBugReport.py from OTB-DevUtils/Scripts
    • Copy/paste the result in the release notes
• Update list of contributors if necessary
• Prepare annoucement email
• Prepare annoucement on the blog

J-1

• Last minute fixes, but avoid if possible
• Before nightly deadline, tag for RC
  • tag OTB
  • tag Monteverdi
  • tag OTB-Wrapping
• Make TGZ source packages
• Make ZIP source packages
• Ensure you named the zipped files with the same convention as the previous release (OTB -> OTB ; Monteverdi -> Monteverdi)
• Test the source packages
• Upload the packages on www.orfeo-toolbox.org/packages

J

• Last dashboard check to confirm the release candidate
• On failure :
  • Remove the source packages from the http server
  • Backout tags
  • Go back J-1
• Copy from www.orfeo-toolbox.org/packages/nightly :
  • Monteverdi Windows installer
  • Monteverdi Mac installer
  • SoftwareGuide PDF
  • Cookbook PDF
  • Cookbook HTML
• Generate SoftwareGuide HTML version (still needs user interaction...)
• Upload the SoftwareGuide HTML version
• Generate Applications HTML version (generated by the Python script generateAppliDoc.py)
• Upload the Applications HTML version and update simlink
• Send RC announcement email (and blog post if there is one)

Final release preparation

J-2

• Find a release code name
• Prepare annoucement email MANUEL
• Prepare annoucement on the blog MANUEL
• Launch doxygen generation (will finish on J)
• Update documentation about installation (version number, packages name, list of supported platform) if necessary
• Launch javadoc generation

J-1

• No last minutes fix allowed
• Test the nightly generated binary packages
• Update date in RELEASE_NOTES.txt
• Before nightly deadline, tag for RC
  • tag OTB
  • tag Monteverdi
  • tag OTB-Applications
  • tag OTB-Wrapping
  • tag OTB-Data
  • tag OTB-Documents
  • tag OTB-DevUtils
• Prepare TGZ source packages
• Prepare ZIP source packages
• Ensure you named the zipped files with the same convention as the previous release
• Upload source packages
• Upload the source packages on sourceforge (OTB, Monteverdi, OTB-Wrapping)
• Update status on freecode.com
• Do some cleanup in the packages dir on orfeo-toolbox if relevant (keep new release, put release candidate packages in 'archives')

J

• Test the generated binary packages in http://www.orfeo-toolbox.org/packages/nightly
• Upload binary packages
  • Monteverdi-windows
  • Monteverdi-MacOS
• Upload Software pdf Guide on orfeo-toolbox
• Upload Cookbook pdf on orfeo-toolbox
• Upload FAQ pdf on orfeo-toolbox
• Upload Software pdf Guide on sourceforge
• Upload Cookbook pdf on sourceforge
• Upload FAQ pdf on sourceforge
• Update OSGeo4W packages
• Generate Ubuntu source packages and upload to launchpad
• Generate rpm packages
• Update direct link on orfeo-toolbox
• Update doxygen on orfeo-toolbox
• Update javadoc on orfeo-toolbox
• Update Software Guide online on orfeo-toolbox
• Update Cookbook online on orfeo-toolbox
• Update FAQ html on orfeo-toolbox
• Generate Applications HTML version (generated by the Python script generateAppliDoc.py)

generateAppliDoc.py  OTB_BIN_DIR APP_DOC_OUTPUT_DIR</s>

• <s>Upload the Applications HTML version and update simlink
• Update OTB-Data-Examples.tgz on orfeo-toolbox (packages)
• Send email to mailing list to announce the release
• Release announcement on the blog

J+1

• Update version number to a development version (even minor number)
• Stop nightly submission to launchpad to avoid flooding the server

J+N

• Update osgeo-live GIS installation script with new OTB versions