Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Acceleo/Retention Policy

< Acceleo
Revision as of 07:02, 12 January 2011 by Unnamed Poltroon (Talk) (categories)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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
Features Acceleo Features · Runtime · Acceleo editor · Views & Perspective · Interpreter · Maven
User documentation Getting Started · User Guide · 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 Professional Support · Report a bug

Back to the top