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 9: | Line 9: | ||
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. | 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 | + | The Eclipse release train is based on the build result of each Eclipse components, checks the Eclipse policies and aggregates them in identified packages. |
== <br>The Polarsys release train == | == <br>The Polarsys release train == | ||
| − | + | The principle of the Polarsys release train is the same than the Eclipse release train except that it uses Eclipse, Polarsys, and LTS components. | |
Revision as of 09:48, 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 is based on the build result of each Eclipse components, checks the Eclipse policies and aggregates them in identified packages.
The Polarsys release train
The principle of the Polarsys release train is the same than the Eclipse release train except that it uses Eclipse, Polarsys, and LTS components.