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 "Polarsys/ReleaseEngineering/Process"
| Line 1: | Line 1: | ||
This section explains the general process of the Polarsys release engineering as depicted below. | This section explains the general process of the Polarsys release engineering as depicted below. | ||
| − | + | [[Image:PolarsysReleaseTrain-ProcessBigPicture.JPG]] | |
| − | + | ||
| − | + | ||
<br> | <br> | ||
| − | == The Eclipse release train == | + | == The Eclipse release train == |
| − | + | Each Eclipse component has its own countinuous integration lifecycle, is responible for the produced artifacts, in compliance with the Eclipse and project policies, and the expected quality level. | |
| − | + | ||
| − | + | ||
| − | + | The Eclipse release train rebuilds all the Eclipse components, checks the Eclipse policies and aggregates them in identified packages. | |
| − | + | == <br>The Polarsys release train == | |
| − | + | [TBD]. | |
Revision as of 09:27, 14 June 2012
This section explains the general process of the Polarsys release engineering as depicted below.
The Eclipse release train
Each Eclipse component has its own countinuous integration lifecycle, is responible for the produced artifacts, in compliance with the Eclipse and project policies, and the expected quality level.
The Eclipse release train rebuilds all the Eclipse components, checks the Eclipse policies and aggregates them in identified packages.
The Polarsys release train
[TBD].