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...)
 
m (categories)
 
(3 intermediate revisions by 2 users not shown)
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.  
Line 12: Line 12:
  
 
Similarly, while developing a milestone, integration builds are kept until the milestone is available, and then are deleted.
 
Similarly, while developing a milestone, integration builds are kept until the milestone is available, and then are deleted.
 +
 +
 +
{{Acceleo-index}}
 +
 +
[[Category:Modeling]]
 +
[[Category:M2T]]
 +
[[Category:Acceleo]]

Latest revision as of 06:02, 12 January 2011

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.



Acceleo Portal
Project Project · Installation · New & noteworthy · Release review · API policy · Retention policy · Next · Checklist
Features Acceleo Features · Runtime · Acceleo editor · Views & Perspective · Debugger · Profiler · Traceability · Wishlist · Interpreter · Maven
User documentation Getting Started · Acceleo operations reference · OCL operations reference · Text Production Rules · Migration From Acceleo 2.x · Best Practices · Videos · FAQ
Developer documentation Source code · How to contribute · Compatibility · MOFM2T specification · OCL specification
Community Conferences · Twitter & Blogs · Professional Support · Report a bug