[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Hi Everyone,
The following is a draft of a Long Term Support (LTS) ready definition.
I'd really appreciate your thoughts and input to make sure it covers the
important aspects of projects that will allow building them in a LTS forge.
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 repository. This repository should be one that is
supported at the Eclipse Foundation. (e.g. Git)
- A build that:
- Can be cloned/checked out with one step
- Is documented
- Is version controlled
- Is automated
- Is deterministic
- Can refer to compilers and other tools from a configurable location
- Capable of building without needing an active Internet connection
- 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)
- Bugs managed in Bugzilla, and possible to have appropriate meta
data to manage and track bugs routed to each LTS release version
Andrew
