Thanks, Rémi,
Actually, the end of August should be OK for me. I should be wrapping up the first feature on my plan by then, so I should be able to hold on to it locally until master is converted.
cW
Sent from my iPhone
Hi Christian,
You’re right for the next 1.0 being on the master branch. We did not have in mind any new developments during summer for next version of Papyrus.
We are focusing on bug fixes, and did not want to merge only bug fixes from branch 0.10.X to master branch with no developments on master branch.
At the end of August, we will probably create this branch.
Does that sound good for you, or do you need to push some new developments right now on master ?
Cheers
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
<image001.png>www.eclipse.org/papyrus
Thanks, Sébastien.
Next question: I don't see any 0.10.1 or 0.10.x maintenance builds in Hudson, and the 0.10.x_core branch in Git has no commits since 5 February, when the repo was in SVN. It seems that development targeting the Papyrus 0.10.1 (Kepler
SR1) release is being done on the master branch, which seems wrong. The master should be for new development targeting Luna, no? Otherwise, how can I start on new features for Luna M2 and M3 milestones?
Nest release of Papyrus will be 1.0.
------------------------------------------------------------------------------------------------------------------------------------------------
+33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47
DILS/Laboratoire d’Ingénierie
dirigée par les modèles pour les Systèmes Embarqués (LISE),
91 191 Gif sur Yvette CEDEX
I have entered some plan items into Bugzilla for enhancements to the CDO integration in Papyrus that I intend to contribute in the Luna release:
The PMI for Papyrus [2] does not appear to have a Luna release record, yet. Will the next release be 0.11 or 1.0? I see that Bugzilla does not have a 0.11 release, but it has a 1.0 release, although it also has several
that don't make sense for Papyrus (e.g., 2.4, 3.1), so I'm not sure that this means anything.
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|