Skip to content

Release 7.4

We are ready to release OTB version 7.4.0. The following steps need to be done:

Scope of the release:

  • !828 (merged): New TerraSarX sensor model, based on the unfinished work of !553 (closed)
  • !833 (merged): Add deprecate tags in preparation for release 8.0.0
  • !838 (merged): ExtractROI: Test points inversion on index instead of coordinate
  • !840 (merged): Remove the "working around a kernel bug" warning during OTB binary package installation
  • !839 (merged): Rename the noise parameter in SARCalibration
  • !831 (merged): bug fixes in Sentinel 1 calibration
  • !836 (merged): Use Horner method for polynomial evaluation in SAR calibration
  • !835 (merged): Update geotiff in the Superbuild
  • !837 (merged): Fix Superbuild compilation with gcc-8
  • backport of !821 (merged): update expat
  • backport of !788 (merged): Fix build issue when libSVM is OFF or libsiftfast is OFF and Testing ON
  • backport of !822 (merged): Update openCV version to 4.5.1 for the SuperBuild

Release Candidate

1. Branches

  • (if major or minor release) Feature freeze: create the new release branch
  • (if patch release) Work on the already existing branch release-7-4
  • Make sure the version number in CMakeLists.txt is 7.4.0

2. Housekeeping

3. Actual release

Once all blocking issues are closed, and the previous steps are done:

4. Publish and plan next release

Release

1. Branches

  • Make sure the version number in CMakeLists.txt is 7.4.0

2. Housekeeping

  • In this story, make a list of blocking issues for the release (if any)
  • Fix compilation warnings on CI
  • Update release notes (walk the GitLab MR merged history and log all improvements)
  • Update the date in RELEASE_NOTES.txt
  • Check SonarQube
  • 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
    • Test QGIS on qgis docker image

3. Actual release

Once all blocking issues are closed, and the previous steps are done:

  • Tag the release
  • (if major or minor release): Merge the release into develop
  • (if it's the latest release): Merge the release into master
  • (if patch release): Backport fixes
  • Update GIT_TAG for all official remote modules (if needed)

4. Publish and plan next release

Edited by Julien Osman