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.
Difference between revisions of "Eclipse/Repository retention policy"
< Eclipse
| Line 3: | Line 3: | ||
The following document describes the retention policy used by the Eclipse Platform: | The following document describes the retention policy used by the Eclipse Platform: | ||
| − | * Release repositories: | + | * Release repositories: The repository contains all the metadata and artifact of a given release (e.g. Galileo) and no content is ever removed from it. When a new SR is made available the metadata and the artifacts are appended to the existing repository. |
* Milestone build repositories: Content is expected to stay until the release is complete. | * Milestone build repositories: Content is expected to stay until the release is complete. | ||
* Integration build repositories: Content is expected to stay until the milestone is complete, but can be disposed at any time. | * Integration build repositories: Content is expected to stay until the milestone is complete, but can be disposed at any time. | ||
* Nightly build repositories: Content can be disposed at any time. | * Nightly build repositories: Content can be disposed at any time. | ||
| + | |||
| + | [[Category:Equinox_p2]] | ||
Revision as of 10:24, 27 October 2009
p2's ability to provision complete products from repositories has made the concept of repositories a first-class citizen of the eclipse ecosystem. People can now use repositories during the build, at development time to setup their target and find missing bundles or simply to setup their IDE. Consequently, repository users expect stability over the content of these repositories and it is important to make clearly available the retention policy associated with each repository.
The following document describes the retention policy used by the Eclipse Platform:
- Release repositories: The repository contains all the metadata and artifact of a given release (e.g. Galileo) and no content is ever removed from it. When a new SR is made available the metadata and the artifacts are appended to the existing repository.
- Milestone build repositories: Content is expected to stay until the release is complete.
- Integration build repositories: Content is expected to stay until the milestone is complete, but can be disposed at any time.
- Nightly build repositories: Content can be disposed at any time.