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
m (Repository retention policy moved to Eclipse/Repository retention policy: Move under Eclipse project namespace) |
|||
| Line 1: | Line 1: | ||
| − | 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 | + | 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 the content of these repositories to be stable, and it is important to make the retention policy of each repository clearly available. |
| − | The following document describes the retention policy used by the Eclipse | + | The following document describes the retention policy used by the [[Eclipse]] Project: |
* 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. | * 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. | ||
| Line 9: | Line 9: | ||
Though specific to the Eclipse platform team, these rules are general enough that we encourage any other team producing repositories to follow them. | Though specific to the Eclipse platform team, these rules are general enough that we encourage any other team producing repositories to follow them. | ||
| + | |||
| + | See also: [[Eclipse_Project_Update_Sites]] | ||
[[Category:Equinox_p2]] | [[Category:Equinox_p2]] | ||
| + | [[Category:Eclipse]] | ||
Revision as of 10:37, 15 March 2010
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 the content of these repositories to be stable, and it is important to make the retention policy of each repository clearly available.
The following document describes the retention policy used by the Eclipse Project:
- 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.
Though specific to the Eclipse platform team, these rules are general enough that we encourage any other team producing repositories to follow them.
See also: Eclipse_Project_Update_Sites