Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Polarsys/ReleaseEngineering/Definitions"

 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Polarsys definitions for release engineering  
+
Definitions for the Polarsys release engineering  
  
*A '''Polarsys release''' is a delivered version of the Polarsys platform, like an Eclipse (e.g., Eclipse 3.x, 4.y).
+
<br>
*A '''Polarsys package''' is an aggregation of built components for a distribution of a Polarsys release, like the "Eclipse Modeling Tools" package.&nbsp;A Package contains a consistent set of integrated components.
+
 
*A '''Polarsys platform''' is a Polarsys package which stresses on the fact that the package is an SDK with a configuration of components.
+
== Component, Package  ==
 +
 
 +
A ''component'' is an Eclipse, Polarsys, or LTS component.  
  
 
<br>  
 
<br>  
  
Kinds of Polarsys platform:  
+
A ''Polarsys package'' is an Eclipse platform enriched by a set of selected and integrated components, to meet a need of Polarsys distribution. By analogy, the "Eclipse Modeling Tools" package is a distribution of Eclipse modeling tools. Examples of Polarsys packages:<br>
 +
 
 +
*''Polarsys Operational Package''&nbsp;(POP): &nbsp;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''&nbsp;(PEP): this package integrates validated components; some are already certified.
 +
 
 +
In the future, Polarsys could be declined in other packages.
 +
 
 +
<br>
  
*'''Polarsys Operational Platform'''&nbsp;(POP): &nbsp;this platform integrates certified components. This platform respects a time-based planning.
+
== Release Planning  ==
*'''Polarsys Experimental Platform'''&nbsp;(PEP): this platform integrates validated components; some are already certified.
+
  
In the future, Polarsys could be declined in other kinds of platforms.
+
A ''Polarsys release planning'' schedules releases of Polarsys packages. Properties of a release: release number and date, released package, the list of integrated components.

Latest revision as of 08:48, 15 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, to meet 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, the list of integrated components.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.