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.
Difference between revisions of "Polarsys/ReleaseEngineering/Process"
| Line 1: | Line 1: | ||
| − | This section | + | This section presents the general process of the Polarsys release engineering as depicted below. |
[[Image:PolarsysReleaseTrain-ProcessBigPicture.JPG]] | [[Image:PolarsysReleaseTrain-ProcessBigPicture.JPG]] | ||
Revision as of 09:48, 14 June 2012
This section presents 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.