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/Definitions"
| Line 1: | Line 1: | ||
| − | Definitions for Polarsys release engineering | + | Definitions for the Polarsys release engineering |
<br> | <br> | ||
| − | == Component, Package == | + | == Component, Package == |
A ''component'' is an Eclipse, Polarsys, or LTS component. | A ''component'' is an Eclipse, Polarsys, or LTS component. | ||
| Line 20: | Line 20: | ||
== Release Planning == | == Release Planning == | ||
| − | A ''Polarsys release planning'' schedules | + | A ''Polarsys release planning'' schedules releases of Polarsys packages. Properties of a release: release number and date, released package with the list of integrated components. |
Revision as of 08:22, 14 June 2012
Definitions for the Polarsys release engineering
Component, Package
A component is an Eclipse, Polarsys, or LTS component.
A Polarsys package is an Eclipse platform enriched by a set of selected and integrated components, according to a need of Polarsys distribution. By analogy, the "Eclipse Modeling Tools" package is a distribution of Eclipse modeling tools. Examples of Polarsys packages:
- Polarsys Operational Package (POP): this package integrates certified components and respects a time-based planning, and especially the Eclipse release train (independently of the VLTS releases).
- Polarsys Experimental Package (PEP): this package integrates validated components; some are already certified.
In the future, Polarsys could be declined in other packages.
Release Planning
A Polarsys release planning schedules releases of Polarsys packages. Properties of a release: release number and date, released package with the list of integrated components.