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
| Line 6: | Line 6: | ||
[https://semver.org/ Nebula uses the major.minor.service version semantics] | [https://semver.org/ Nebula uses the major.minor.service version semantics] | ||
| + | |||
| + | == New Minor Release Checklist == | ||
| + | A minor release is a new release without an API break. The Minor Release versioning updates the second number e.g. 2.7.0 -> 2.8.0 | ||
| + | * [[Nebula/Releases/New Release/announce service release on the mailing list|Announce the service release on the mailing list]] | ||
| + | * [[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 Github artifacts for a minor release|Add Bugzilla Artifacts for a Minor 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/update the version in the nebula main feature|Update the version in the main feature]] | ||
| + | * [[Nebula/Releases/New Release/cherry-pick the changes|Cherry-pick the changes on a working branch]] | ||
| + | * [[Nebula/Releases/New Release/make pull request in github|Create a PR in Github (but do not merge)]] | ||
| + | * [[Nebula/Releases/New Release/update the build configuration|Update the Build configuration]] | ||
| + | * [[Nebula/Releases/New Release/promote a build candidate|Promote a build candidate]] | ||
| + | * [[Nebula/Releases/New Release/announce and test the release candidate|Announce and Test the Candidate]] | ||
| + | * [[Nebula/Releases/New Release/update the website|Update the Website]] | ||
| + | * [[Nebula/Releases/New Release/add the release to github|Add the Release to Github]] | ||
| + | * [[Nebula/Releases/New Release/close github milestone|Close the Github Milestone]] | ||
| + | * [[Nebula/Releases/New Release/update the nan|Update the NAN]] | ||
| + | * [[Nebula/Releases/New Release/announce success|Announce Success]] | ||
| + | |||
| + | |||
== New Service Release Checklist == | == New Service Release Checklist == | ||
| + | A Service Release is to fix a bug in the minor release. Service releases have the third number of the release set. e.g. 2.7.0 -> 2.7.1 | ||
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. | 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. | ||
| Line 28: | Line 50: | ||
* [[Nebula/Releases/New Release/update the nan|Update the NAN]] | * [[Nebula/Releases/New Release/update the nan|Update the NAN]] | ||
* [[Nebula/Releases/New Release/announce success|Announce Success]] | * [[Nebula/Releases/New Release/announce success|Announce Success]] | ||
| − | |||
| − | |||
| − | |||
Revision as of 15:07, 3 February 2022
This page describes how to create a new release.
Nebula uses the major.minor.service version semantics
New Minor Release Checklist
A minor release is a new release without an API break. The Minor Release versioning updates the second number e.g. 2.7.0 -> 2.8.0
- Announce the service release on the mailing list
- Create a service release in the project administration
- Add Bugzilla Artifacts for a Minor 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
New Service Release Checklist
A Service Release is to fix a bug in the minor release. Service releases have the third number of the release set. e.g. 2.7.0 -> 2.7.1 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