Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Nebula/Releases/New Release"
< Nebula
(→New Service Release Checklist) |
(→New Minor Release Checklist) |
||
| Line 31: | Line 31: | ||
== New Minor Release Checklist == | == New Minor Release Checklist == | ||
| − | * [[Nebula/Releases/New Release/add bugzilla artifacts for a minor release|Add Bugzilla | + | * [[Nebula/Releases/New Release/add bugzilla artifacts for a minor release|Add Bugzilla Artifacts for a Minor Release]] |
Revision as of 15:33, 3 October 2020
This page describes how to create a new release.
Nebula uses the major.minor.service version semantics
New Service Release Checklist
The following steps are needed to create a new Nebula Service Release. To avoid unneeded risks, you must cherry-pick your changes on top of the latest released tag.
Before you start, open a new workspace and import [https://github.com/eclipse/nebula/blob/master/releng/org.eclipse.nebula.feature/Nebula_All.psf this project set via Import/Team/Team Project Set.
Cherry-picking movie
- Announce the service release on the mailing list
- Create a service release in the project administration
- Add Bugzilla artifacts for a Service Release
- Create a Release Bug
- Classify bugs
- Update the version in the main feature
- Cherry-pick the changes on the latest released Tag
- Create a PR in Github (but do not merge)
- Update the Build configuration
- Promote a build candidate
- Announce and Test the Candidate
- Update the Website
- Add the Release to Github
- Update the NAN
- Update the project set file with any new plugins