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"
(It is no longer possible to prioritize newest bugs, so next milestone can't be default) |
|||
| Line 12: | Line 12: | ||
<code>git pull origin release/version -s ours</code> | <code>git pull origin release/version -s ours</code> | ||
* 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]] | ||
[[Category:RCPTT]] | [[Category:RCPTT]] | ||
Revision as of 10:40, 28 April 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:
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