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 "Nebula/Releases/New Release"
(→Minor Release) |
(→New Release Checklist) |
||
Line 6: | Line 6: | ||
The following steps are needed to create a new Nebula Release. | The following steps are needed to create a new Nebula Release. | ||
− | * Announce | + | * [[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]] |
− | * Add Bugzilla artifacts | + | * [[Nebula/Releases/New Release/add bugzilla artifacts minor|Add Bugzilla artifacts]] |
− | * Create a Release Bug | + | * [[Nebula/Releases/New Release/rreate a release bug|Create a Release Bug]] |
− | * Classify bugs | + | * [[Nebula/Releases/New Release/classify bugs|Classify bugs]] |
− | * Update the version in the | + | * [[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 build configuration|Update the Build configuration]] |
− | * Promote a build candidate | + | * [[Nebula/Releases/New Release/promote a build candidate|Promote a build candidate]] |
− | * Release the | + | * [[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]] |
− | * Add Release to Github | + | * [[Nebula/Releases/New Release/add the release to github|Add the Release to Github]] |
− | * | + | * [[Nebula/Releases/New Release/update the nan|Update the NAN]] |
− | * Update the project set file with any new plugins | + | * [[Nebula/Releases/New Release/update the project set file|Update the project set file with any new plugins]] |
== Announce your plans on the mailing list == | == Announce your plans on the mailing list == |
Revision as of 12:34, 3 October 2020
This page describes how to create a new release.
Nebula uses the major.minor.service version semantics
Contents
New Release Checklist
The following steps are needed to create a new Nebula Release.
- Announce the service release on the mailing list
- Create a service release in the project administration
- Add Bugzilla artifacts
- Create a Release Bug
- Classify bugs
- Update the version in the main feature
- 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
Announce your plans on the mailing list
Announce your plan on the mailing list and describe that a new release is imminent. The project lead will be involved in some of the steps. The date of the release will be no shorter than 7 days after the announcement.
Create a project in the project administration
The project lead defines the release here [1]. The project lead
Add Bugzilla Artifacts
Add Bugzilla artifacts via your eclipse user profile page. Once logged in to Eclipse the Bugzilla artifacts page can be found here: [2]
Service Release
For a service release, we must add a new milestone. If the current version is 2.4.2 then the new milestone must be 2.4.3. Take care when adding version and milestones because the page does not allow mistakes:
In Bugzilla Management press the Edit button
Press "Add bugzilla milestones .."
In the window that appears, add the service release milestone. Make sure that the sort key matches the version number. You get one chance to do it right. If you make a mistake then you must as the webmaster to correct it.
Leave the default milestone to the new version.
Minor Release
For a minor release, we must add a new milestone and a new version after the release is released. If the current version is 2.5.1 then a new milestone must be 2.7.0 and a "new" version must be 2.6.0. The new milestone points to the next next release. Take care when adding version and milestones because the page does not allow mistakes:
In Bugzilla Management press the Edit button
Press "Add bugzilla milestones .."
In the window that appears, add the service release milestone. Make sure that the sort key matches the version number. You get one chance to do it right. If you make a mistake then you must as the webmaster to correct it.
From the Bugzilla Management screen, select "add Bugzilla versions...":
Next, add the new version by pressing on the "Add a new version" link:
Add the new version. Take care to make no mistakes. If you do make a mistake you must ask the webmaster to correct it.
From the Bugzilla Management screen, make the new version the default milestone:
Bugzilla
Create a bug for this release:
Add Bugzilla Artifacts
Add Bugzilla artifacts via your eclipse user profile page