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) |
|||
| Line 15: | Line 15: | ||
* [[Nebula/Releases/New Release/create a service release in the project administration|Create a service release in the project administration]] | * [[Nebula/Releases/New Release/create a service release in the project administration|Create a service release in the project administration]] | ||
* [[Nebula/Releases/New Release/add bugzilla artifacts service|Add Bugzilla artifacts for a Service Release]] | * [[Nebula/Releases/New Release/add bugzilla artifacts service|Add Bugzilla artifacts for a Service Release]] | ||
| − | * [[Nebula/Releases/New Release/ | + | * [[Nebula/Releases/New Release/Create a release bug|Create a Release Bug]] |
* [[Nebula/Releases/New Release/classify bugs|Classify bugs]] | * [[Nebula/Releases/New Release/classify bugs|Classify bugs]] | ||
* [[Nebula/Releases/New Release/update the version in the nebula main feature|Update the version in the main feature]] | * [[Nebula/Releases/New Release/update the version in the nebula main feature|Update the version in the main feature]] | ||
Revision as of 14:45, 3 February 2022
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 this project set via Import/Team/Team Project Set.
- 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 a working branch
- 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
- Close the Github Milestone
- Update the NAN
- Announce Success