OCL/Dev/Policies

Eclipse OCL doesn't have any special project-specific API retention policy, so it follows the general Eclipse Project guidelines on API deprecation and removal

For ZIP file distributions which are downloadable from the project downloads web page:

Formal/Official Release distributions (including service releases) will be available for as long as the corresponding Eclipse platform is available.
Milestone and Release Candidate distributions which are stable versions preceding a release. After the M3 milestone, the three most recent distributions will be available.
Integration/Interim distributions are used between milestones. When a new milestone distribution appears, integration distributions are removed (the last one is always kept).
Nightly distribution are usually generated from nightly builds for internal purposes. There is no guarantee of any retention.

For the P2 repositories, the following policy applies:

Formal/Official Release P2 repositories are kept for as long as the corresponding Eclipse platform is available.
- Helios Release P2 repository: http://download.eclipse.org/modeling/mdt/ocl/3_0/updates/
The three most recent Milestone and Release Candidate P2 repositories are kept until the Official release arrives.
- Indigo Milestones P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/3.1.0/
We only keep one P2 repository with the last integration build.
- Indigo Interim P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/interim/3.1.0/
We only keep one P2 repository with the last nightly build.
- Indigo Nightly P2 repository: http://download.eclipse.org/modeling/mdt/ocl/updates/nightly/3.1.0/

N.B: This policy has been created the 24th, December, 2010. Last update: the 12th, January, 2011.

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.