[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mdt-ocl.dev] RE: Backwards compatibility for MDT OCL
|
Hi Kenn and
Nick,
The MDT OCL team has
decided to implement the new OCL standard (2.2) and also to support backwards
compatibility with the current implementation of the OCL 2.0 standard. Since the
new and the old OCL standards are not compatible we have decided to create two
initially similar sets of plugins/features - MDT OCL 1.4.0 (for backwards
compatibility in Helios+ releases) and MDT OCL 3.0.0 (the new
implementation of OCL 2.2). We think it would be convenient to make a CVS branch
for 1.4.0, and thus, to build 3.0.0 artefacts from HEAD and release 1.4.0
artefacts from the branch.
Plugins for 1.4.0
and 3.0.0 are to be independent and must successfully co-exist in Helios.
Ideally, 1.4.0 and 3.0.0 plugins should be in different components -
so that the users have the option not only to install both implementations but
also to install only one of them.
Kenn, is it ok for
MDT OCL to split into two components?
Nick, do you forsee
any difficulties in releng (releasing 3.0.0 from HEAD and 1.4.0 from
branch)?
Thanks,
Alex.
