Hi Benoit, hi all,
Although we at Esterel welcome the move to SysML 1.4 (that's great!),
we would kindly ask you to consider *not* removing support for good old SysML 1.1 from Neon.
The rationale for this request is twofold:
-First, given the (numerous and significant) updates done in the core of Papyrus 2.0,
migrating to Papyrus 2.0 will be a lot of work for "consumers" that build tools upon Papyrus.
We would rather migrate to Papyrus 2.0 while keeping our SysML 1.1 basis unchanged for now,
in order to have a smoother migration experience and not mix unrelated problems along the way.
-Second, as the migration tool from SysML 1.1 to SysML 1.4 is not yet available,
we find it a bit premature to force the switch to SysML 1.4 onto tool providers and end users.
We need to assess the new SysML 1.4 components *and the migration tool* on our side before committing to SysML 1.4, in order to make sure that the migration is actually flawless and smooth for our end users.
Thanks in advance for your understanding.