Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RCPTT/Release procedure"
Line 13: | Line 13: | ||
* If release version was newly created, [https://git.eclipse.org/c/rcptt/org.eclipse.rcptt.git/tree/update_version.sh bump] version of source base in master branch | * If release version was newly created, [https://git.eclipse.org/c/rcptt/org.eclipse.rcptt.git/tree/update_version.sh bump] version of source base in master branch | ||
* [[SimRel/Overview|Contribute new release update site to simrel]] | * [[SimRel/Overview|Contribute new release update site to simrel]] | ||
+ | * Observe simrel [https://ci.eclipse.org/oomph/job/repository-analyzer/ validation reports] | ||
[[Category:RCPTT]] | [[Category:RCPTT]] |
Revision as of 10:31, 4 May 2022
- Create a release branch if not already present
- Test branch by running branch build with parameter GERRIT_REFSPEC = "refs/heads/release/version"
- Publish release with parameters: GERRIT_REFSPEC = "refs/heads/release/version", MODE = "release"
- Update download page
- Create next Eclipse portal release
- Create Bugzilla release
- Create next Bugzilla milestone
- Move unresolved bugs from released milestone to next milestone
- Create next Bugzilla milestone
- Bump minor release version in release branch (if not first release from that branch)
- Merge bump commit to master. Null out bump commit if master is already working on next release.
git pull origin release/version -s ours
- If release version was newly created, bump version of source base in master branch
- Contribute new release update site to simrel
- Observe simrel validation reports