Jump to: navigation, search

Difference between revisions of "Acceleo/Retention Policy"

(New page: = Retention Policy for Acceleo builds = == Code in CVS == Any code that was built and included in a Release is left in CVS forever. The CVS history allows for the retrieval of the code f...)
 
Line 5: Line 5:
 
Any code that was built and included in a Release is left in CVS forever. The CVS history allows for the retrieval of the code for each specific version, each tagged with a convenience tag such as "maintenance_R3_0".
 
Any code that was built and included in a Release is left in CVS forever. The CVS history allows for the retrieval of the code for each specific version, each tagged with a convenience tag such as "maintenance_R3_0".
  
=== Distributions in zip files ===
+
== Distributions in zip files ==
  
 
Formal releases are kept forever, but only the most recent release is kept on the [http://www.eclipse.org/modeling/m2t/downloads/?project=acceleo main download page]. Other, older distributions can be found on the archives site.  
 
Formal releases are kept forever, but only the most recent release is kept on the [http://www.eclipse.org/modeling/m2t/downloads/?project=acceleo main download page]. Other, older distributions can be found on the archives site.  

Revision as of 04:20, 2 June 2010

Retention Policy for Acceleo builds

Code in CVS

Any code that was built and included in a Release is left in CVS forever. The CVS history allows for the retrieval of the code for each specific version, each tagged with a convenience tag such as "maintenance_R3_0".

Distributions in zip files

Formal releases are kept forever, but only the most recent release is kept on the main download page. Other, older distributions can be found on the archives site.

While developing a new release, milestone builds are kept until the release, at which point they are deleted.

Similarly, while developing a milestone, integration builds are kept until the milestone is available, and then are deleted.