Difference between revisions of "LTS/LTS Ready"

From Eclipsepedia

< LTS
Jump to: navigation, search
(New page: The following are the minimum required in order to be considered Long Term Support (LTS) ready: * A distributed version control system capable of pushing branches from repository to repos...)
 
Line 1: Line 1:
 
The following are the minimum required in order to be considered Long Term Support (LTS) ready:
 
The following are the minimum required in order to be considered Long Term Support (LTS) ready:
  
 +
==Code Repository==
 
* A distributed version control system capable of pushing branches from repository to repository. This repository should be one that is supported at the Eclipse Foundation. (e.g. Git)
 
* A distributed version control system capable of pushing branches from repository to repository. This repository should be one that is supported at the Eclipse Foundation. (e.g. Git)
* A build that
+
 
 +
==Build==
 +
A build that
 
## Can be cloned/checked out with one step
 
## Can be cloned/checked out with one step
 
## Is documented
 
## Is documented
Line 13: Line 16:
 
## Capable of pulling dependencies from a known controlled source (e.g. Orbit, Maven, eclipse.org, etc.)
 
## Capable of pulling dependencies from a known controlled source (e.g. Orbit, Maven, eclipse.org, etc.)
 
## Adheres to Eclipse IP policies (esp. with regards to third party code)
 
## Adheres to Eclipse IP policies (esp. with regards to third party code)
 +
 +
==Bug Tracking==
 
* Bugs managed in Bugzilla, and possible to have appropriate meta data to manage and track bugs routed to each LTS release version
 
* Bugs managed in Bugzilla, and possible to have appropriate meta data to manage and track bugs routed to each LTS release version
 +
 +
==Release Management==
 
* Was released as part of the annual simultaneous release
 
* Was released as part of the annual simultaneous release

Revision as of 15:32, 6 February 2012

The following are the minimum required in order to be considered Long Term Support (LTS) ready:

Contents

Code Repository

  • A distributed version control system capable of pushing branches from repository to repository. This repository should be one that is supported at the Eclipse Foundation. (e.g. Git)

Build

A build that

    1. Can be cloned/checked out with one step
    2. Is documented
    3. Is version controlled
    4. Is automated
    5. Is deterministic given the same source code and third party libraries
    6. Is easily reproducible on suitably-configured systems TODO: Can we define this a little better?
    7. Can refer to compilers and other tools from a configurable location
    8. Capable of building without needing an active Internet connection
    9. Capable of pulling dependencies from a known controlled source (e.g. Orbit, Maven, eclipse.org, etc.)
    10. Adheres to Eclipse IP policies (esp. with regards to third party code)

Bug Tracking

  • Bugs managed in Bugzilla, and possible to have appropriate meta data to manage and track bugs routed to each LTS release version

Release Management

  • Was released as part of the annual simultaneous release