Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Papyrus M6
Thanks, Camille.

There would also be bug 402961 [1], should you choose to merge it in M7, which would change the ConfigurationManager API and the context and preferences models in the Properties View plug-ins.

Of course, this merge could even wait until Luna, as it isn't vitally important for CDO integration.

cW




On 2013-03-19, at 10:18 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:

Hi all,
 
Tomorrow, we will build the M6 for Papyrus. M6 corresponds to the API freeze. In theory, all major changes to the Papyrus API have already been integrated, and from now on, there shouldn’t be any surprise for M6.
 
However, we’ve already planned to change a few APIs after M6, in the following area:
 
-          ReadOnly support (ReadOnlyHandler, ReadOnlyManager)
-          ControlMode API
 
The new service registry implementation/API should also be integrated between M6 and M7, but the current service implementations will still be compatible, so I guess this is not really an API change.
 
To all Papyrus committers: if you still plan some major API changes, please wait after M6 (And let me know ASAP). As the build is tomorrow, and as we plan API changes anyway, I really prefer to avoid integrating them in hurry tomorrow.
 
I also remind everyone that M7 is the feature-freeze milestone, and the last 4 weeks should be dedicated to bug-fixes only.
 
 
Thank you,
Camille
__________________________
Camille Letavernier
+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx
CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)
 
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

Back to the top