Difference between revisions of "Eclipse/Repository retention policy"

From Eclipsepedia

Jump to: navigation, search
 
(4 intermediate revisions by 2 users not shown)
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 stability over the content of these repositories and it is important to make clearly available the retention policy associated with each repository.
+
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 Platform:
+
The following document describes the retention policy used by the [[Eclipse]] Project:
  
* Release repositories: Content is expected to be immutable.  
+
* 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.
 +
 
 +
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:Eclipse]]

Latest 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