Difference between revisions of "LTS/LTS Ready"
From Eclipsepedia
< LTS
(→Build) |
m (→Build) |
||
| Line 18: | Line 18: | ||
## does it even need an eclipse SDK install? If so, I'd suggest Indigo as a baseline | ## does it even need an eclipse SDK install? If so, I'd suggest Indigo as a baseline | ||
# Can refer to compilers and other tools from a configurable location '''suggestion:''' | # Can refer to compilers and other tools from a configurable location '''suggestion:''' | ||
| − | ## must be able to supply JRE locations for 1.4-1.7 | + | ## must be able to supply JRE locations for 1.4-1.7 Kim: We compile against the following libaries Foundation 1.0, Foundation 1.1, See the execution environment on a per bundle basis in the [http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_2.xml#appendix project plan]. |
## to support the next requirement, must be able to supply local mirrors of required p2 repositories (orbit, indigo/juno, etc) | ## to support the next requirement, must be able to supply local mirrors of required p2 repositories (orbit, indigo/juno, etc) | ||
## signing at eclipse.org needs to be optional but configurable? | ## signing at eclipse.org needs to be optional but configurable? | ||
Revision as of 11:45, 7 February 2012
The following are the minimum required in order for a project 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
- Can be cloned/checked out with one step
- Is documented
- Is version controlled
- Is automated
- Is deterministic given the same source code and third party libraries
- Is easily reproducible on suitably-configured systems TODO: Can we define this a little better? suggestion:
- has git >=1.7
- has java >=6.0
- has maven 3.0.3
- does it even need an eclipse SDK install? If so, I'd suggest Indigo as a baseline
- Can refer to compilers and other tools from a configurable location suggestion:
- must be able to supply JRE locations for 1.4-1.7 Kim: We compile against the following libaries Foundation 1.0, Foundation 1.1, See the execution environment on a per bundle basis in the project plan.
- to support the next requirement, must be able to supply local mirrors of required p2 repositories (orbit, indigo/juno, etc)
- signing at eclipse.org needs to be optional but configurable?
- Capable of building without needing an active Internet connection question:
- does maven/tycho cache the bundles it needs from p2 repos in the local maven repo, so having run once you don't need your connection anymore?
- 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)
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