How to Release 3.12

Release Candidate preparation

J-2

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

J-1

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

J

• [DONE] 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 :
  • [DONE] Monteverdi Windows installer
  • [DONE] Monteverdi Mac installer
  • [DONE] SoftwareGuide PDF
  • [DONE] Cookbook PDF
  • [DONE] Cookbook HTML
• [DONE] Generate SoftwareGuide HTML version (still needs user interaction...)
• [DONE] Upload the SoftwareGuide HTML version
• [DONE] Send RC announcement email

Final release preparation

J-2

• [DONE] Find a release code name
• [DONE] Prepare annoucement email
• [DONE] Prepare annoucement on the blog
• [DONE] Launch doxygen generation (will finish on J)
• Launch javadoc generation

J-1

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

J

• [DONE] Test the generated binary packages in http://www.orfeo-toolbox.org/packages/nightly
• [DONE] Upload binary packages
  • [DONE] Monteverdi-windows
  • [DONE] Monteverdi-MacOS
• [DONE] Upload Software pdf Guide on orfeo-toolbox
• [DONE] Upload Cookbook pdf on orfeo-toolbox
• [DONE] Upload FAQ pdf on orfeo-toolbox
• [DONE] Upload Software pdf Guide on sourceforge
• [DONE] Upload Cookbook pdf on sourceforge
• [DONE] Upload FAQ pdf on sourceforge
• [DONE] Update OSGeo4W packages
• Generate Ubuntu source packages and upload to launchpad
• Generate rpm packages
• Update direct link on orfeo-toolbox
• [DONE] Update doxygen on orfeo-toolbox
• Update javadoc on orfe-toolbox
• [DONE] Update Software Guide online on orfeo-toolbox
• [DONE] Update Cookbook online on orfeo-toolbox
• [DONE] Update FAQ html on orfeo-toolbox
• [DONE] Update OTB-Data-Examples.tgz on orfeo-toolbox (packages)
• [DONE] Send email to mailing list to announce the release
• [DONE] Release announcement on the blog

J+1

• [DONE] Update version number to a development version (even minor number)

J+N

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