|
|
| Line 1: |
Line 1: |
| | + | __TOC__ |
| | + | |
| | + | |
| | + | |
| | This page describes how to create a new release. | | This page describes how to create a new release. |
| | | | |
| Line 19: |
Line 23: |
| | * [[Nebula/Releases/New Release/update the nan|Update the NAN]] | | * [[Nebula/Releases/New Release/update the nan|Update the NAN]] |
| | * [[Nebula/Releases/New Release/update the project set file|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 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|border|600px]]
| |
| − |
| |
| − |
| |
| − | Press "Add bugzilla milestones .."
| |
| − |
| |
| − | [[file:bugz2.png|600px|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|border|600px]]
| |
| − |
| |
| − | 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
| |
| − |
| |
| − | [[file:bugz1.png|600px|border]]
| |
| − |
| |
| − |
| |
| − | Press "Add bugzilla milestones .."
| |
| − |
| |
| − | [[file:bugz2.png|600px|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|600px|border]]
| |
| − |
| |
| − |
| |
| − | From the Bugzilla Management screen, select "add Bugzilla versions...":
| |
| − |
| |
| − | [[file:bugz5.png|600px|border]]
| |
| − |
| |
| − |
| |
| − | Next, add the new version by pressing on the "Add a new version" link:
| |
| − |
| |
| − | [[file:bugz6.png|600px|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:bugz7.png|600px|border]]
| |
| − |
| |
| − |
| |
| − | From the Bugzilla Management screen, make the new version the default milestone:
| |
| − |
| |
| − | [[file:bugz8.png|600px|border]]
| |
| − |
| |
| − | == Bugzilla ==
| |
| − | Create a bug for this release:
| |
| − |
| |
| − |
| |
| − |
| |
| − | === Add Bugzilla Artifacts===
| |
| − | Add Bugzilla artifacts via your eclipse user profile page
| |
This page describes how to create a new release.
