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.
Sirius/Compatibility and Migration
< Sirius
Revision as of 11:26, 21 November 2013 by Pierre-charles.david.obeo.fr (Talk | contribs) (Created page with "This page documents the compatiblity policy for Sirius releases, both for users of the Viewpoint technology (the previous name of Sirius) who want to switch to Sirius and from...")
This page documents the compatiblity policy for Sirius releases, both for users of the Viewpoint technology (the previous name of Sirius) who want to switch to Sirius and from new adopters of Sirius itself.
Contents
Background
Overview of the Sirius Releases Roadmap Until 1.0
Objective and General Rules
In general incompatible changes between two versions should be the exception and not the general rule. Any incompatible change should be clearly justified and its impacts minimized.
The rules:
- whenever possible, allow seamless and transparent migration;
- if that is not possible, provide automated or semi-automated tools to assist in the migration. These tools should be usable programmatically (no just by UI actions) to allow users with lots of existing data to automate the migration.
- if automation is not possible or considered too costly, provide complete documentation of the manual steps to perform to migrate existing projects.
In all cases (even when the migration can be handled transparently), all changes should be clearly documented in the release notes of the release or milestone in which they appear first.
Types of Compatibility Issues
- VSM
- Representations Files
- Modeling Projects
- Plug-in dependencies
- Extension points and other ids
- Java namespaces
- Java APIs
Migration Paths
General Rules
=== Migrating from