Patch procedure

• Create Eclipse portal release if it does not exist yet.
  • Copy Project Plan/Target Environments section from the previous release of this minor version.
• Wait for a branch build to pass. Ensure the build passes.
  • There are no Junit test failures.
  • There are no RCPTT test failures.
• Publish releasewith parameters: GERRIT_REFSPEC = "refs/heads/release/version", MODE = "release"
• Validate the update site

  devenv/scripts/check_repository.sh https://download.eclipse.org/rcptt/release/2.7.3/repository/
  

  • Inspect ${TMPDIR}/*/p/index.html (see script output for exact directory)
• Update download page
  • Modify only main branch
  • Master branch is updated and appears on the site automagically.
• Set final release date on release page (Basics section)
• Tag the release commit with "release/x.y.z"
• Bump minor release version in release branch (unless patch 0)
  • Merge bump commit to master. Null out bump commit in the next maintenance branch. git pull origin release/version -s ours

Previous, obsolete procedure