Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Nebula/Releases/New Release"

(→‎Service Release)
(→‎New Minor Release Checklist)
 
(33 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
This page describes how to create a new release.
+
__TOC__
  
−
[https://semver.org/ Nebula uses the major.minor.service version semantics]
 
  
−
== New Release Checklist ==
 
−
The following steps are needed to create a new Nebula Release.
 
−
 
−
* Announce your plans on the mailing list
 
−
* Create a project in the project administration
 
−
* Add Bugzilla artifacts
 
−
* Create a Release Bug
 
−
* Classify bugs included in this release
 
−
* Update the version in the Nebula main feature
 
−
* Update the build configuration
 
−
* Promote a build candidate and test
 
−
* Release the build after the test
 
−
* Update the website
 
−
* Add Release to Github
 
−
* Create a NaN page for the new minor or major version
 
−
* 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 [https://projects.eclipse.org/projects/technology.nebula]. 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: [https://dev.eclipse.org/committers/bugs/bugz_manager.php]
 
−
 
−
=== 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
 
−
 
−
[[file:bugz1.png|500px|border]]
 
−
 
−
 
−
Press "Add bugzilla milestones .."
 
−
 
−
[[file:bugz2.png|500px|border]]
 
−
 
−
 
−
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.
 
−
 
−
[[file:bugz3.png]]
 
−
 
−
Leave the default milestone to the new version.
 
−
 
−
=== Minor Release ===
 
−
For a minor release, we must add a new milestone and a new version. If the current version is 2.5.1 then the new milestone must be 2.7.0 and the 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
 
−
 
−
[[file:bugz1.png|500px|border]]
 
−
 
−
 
−
Press "Add bugzilla milestones .."
 
−
 
−
[[file:bugz2.pgm|500px|border]]
 
−
 
−
 
−
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.
 
−
 
−
[[file:bugz4.png|500px|border]]
 
−
 
−
 
−
From the Bugzilla Management screen, select "add bugzilla versions...":
 
−
 
−
[[file:bugz5.png|500px|border]]
 
−
 
−
 
−
Next, add the new version by pressing on the "Add a new version" link:
 
−
 
−
[[file:bugz5.png|500px|border]]
 
−
 
−
 
−
Add the new version. Take care to make no mistakes. If you do make a mistake you must ask the webmaster to correct it.
 
−
 
−
[[file:bugz6.png|500px|border]]
 
−
 
−
 
−
From the Bugzilla Management screen, make the new version the defaut milestone:
 
−
 
−
[[file:bugz7.png|500px|border]]
 
  
 +
This page describes how to create a new release.
  
 +
[https://semver.org/ Nebula uses the major.minor.service version semantics]
  
−
== Bugzilla ==
+
== New Minor Release Checklist ==
−
Create a bug for this release:
+
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 release on the mailing list|Announce the 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 bugzilla artifacts for a minor release|Add GitHub 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 build configuration|Update the Build configuration]]
 +
* [[Nebula/Releases/New Release/update the version in the nebula main feature|Update the version in the main feature]]
 +
* [[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 ==
 +
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 [https://github.com/eclipse/nebula/blob/master/releng/org.eclipse.nebula.feature/Nebula_All.psf this project set] via '''Import/Team/Team Project Set'''.
  
−
=== Add Bugzilla Artifacts===
+
* [[Nebula/Releases/New Release/announce service release on the mailing list|Announce the service release on the mailing list]]
−
Add Bugzilla artifacts via your eclipse user profile page
+
* [[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 GitHub artifacts for a Service 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]]

Latest revision as of 15:19, 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

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.

Retrieved from "https://wiki.eclipse.org/index.php?title=Nebula/Releases/New_Release&oldid=444785"

This page was last modified 15:19, 3 February 2022 by Wim Jongman.

Back to the top