You'll find the roadmap document attached
with this version numbering.
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De
la part de Jacques LESCOT
Envoyé : vendredi 20 février
2009 14:05
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev]
Papyrus roadmap
Yes, this kind of versioning really fits to what is
done in other Eclipse projects.
TANGUY Yann 176637 a
écrit :
Thanks Jacques.
Based on your previous mail, I propose this numbering for Papyrus plan :
R = Release
M = Milestone
R for 0.7.0 is not simultaneous with e3.5 release delivery.
Mi for 0.7.0 are internal milestones (no link with e3.5 milestones)
We plan to follow the e3.6 development train for 0.8.0 release.
Hopefully we should leave the incubation phase after 0.8.0. Exiting the incubation phase during e3.6 is not realistic in my opinion.
[0.7.0] M1 : 01/05/2009 (M does not refer to e3.5 Milestone)
[0.7.0] M2 : 03/07/2009
[0.7.0] R : 18/09/2009
[0.8.0] R : e3.6 (06/xx/2010)
[1.0.0] R : e3.7 (06/xx/2011)
Does it appear to be a correct radmap from an Eclipse view ?
Regards,
Yann
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Jacques LESCOT
Envoyé : jeudi 19 février 2009 10:11
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Papyrus roadmap
Hi Papyrus team,
My little contribution about Eclipse Guidelines on the versioning of
plugins and features : 0.7.0.2 is not a valid version.
Have a look at the following page for more details :
http://wiki.eclipse.org/index.php/Version_Numbering
You should probably target a 0.7.0 version during the Galileo train
(even if you won't be part of the Galileo simultaneaous release).
Then, you can change to 0.8.0 (or 1.0.0 if you plan to exit from
incubation phasis) version during the 3.6 developments.
Regards,
Jacques
TESSIER Patrick 202707 a écrit :
Hi,
I think that there are mistakes in he document.
You have written funtionnalities to achieve for the version 0.7.0.2 and then you write the funtionnality for the version 0.9 with the same deadline.
---------------------------------------------------------
Patrick Tessier
Research Engineer
DRT LIST/DTSI/SOL/LISE CEA-Saclay
91191 Gif sur Yvette Cedex
Tel: 01 69 08 48 63
www.papyrusuml.org <http://www.papyrusuml.org/>
---------------------------------------------------------
________________________________
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien 166342
Envoyé : mardi 17 février 2009 18:36
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Papyrus roadmap
Here is the roadmap I propose to put on the wiki. I have integrated the comments of Etienne (I hope so indeed). Send me other if you have.
For ALL: send me your feedback soon please and look inside the doc, because some of you needs to clarify/complete some points.
Thanks,
Cheers... Sébastien.
Dr. Sébastien Gérard
Head of MDD for DRES research project
CEA LIST/LISE
Boîte courrier 65, GIF SUR YVETTE
CEDEX, F-91191 France
Phone/fax : +33 1 69 08 58 24 / 83 95
Leader of the Eclipse Component Papyrus (The UML2 Graphical Modeler): www.papyrusuml.org
http://www.eclipse.org/modeling/mdt/?project=papyrus
Before printing, think about the environment
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--
|
|
|
Jacques LESCOT
Project
Manager
Eclipse Technical Expert
jacques.lescot@xxxxxxxxxxxxxxxx
Standard : +33(0)5 61 00 52 90
Direct : +33(0)5 61 00 06 60
Mobile : +33(0)6 74 49 23 34
Fax : +33(0)5 61 00 51 46
|
Anyware Technologies
Lake Park
ZAC de
l'Hers - Allée du Lac
BP 87216
31672 Labège Cedex
France
www.anyware-tech.com
|
|
This message and any attachments (the "Message") are
confidential and intended solely for the addressees.
Any unauthorized modification, edition, use or dissemination is prohibited.
Neither Anyware Technologies nor its headquarters Wavecom shall be liable for
the Message if altered, changed, falsified or edited, diffused without
authorization.
