RE: [mdt-papyrus.dev] Papyrus: versioning

["Kenn Hussey" <Kenn.Hussey@xxxxxxxxxxxxxxx>]

Sebastien,

 

Are these versions intended to correspond to plug-in/feature versions? It’s more typical to have one release per year, or at the very least give yourself some buffer room to allow a version between this year’s and next year’s release. Note that the project will not be allowed to use a version of 1.0 until it exits incubation; generally it takes a couple of major releases (e.g. years) to get to this stage of maturity…

 

Cheers,

 

Kenn Hussey
Program Manager, Modeling and Design Solutions

Embarcadero Technologies, Inc. | www.embarcadero.com 
82 Peter Street, Second Floor | Toronto, ON  M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105

 

From: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] On Behalf Of GERARD Sebastien 166342
Sent: Friday, February 06, 2009 9:31 AM
To: Papyrus Project list
Subject: [mdt-papyrus.dev] Papyrus: versioning

 

Hi all,

 

Following our discussion about the versioning of Papyrus, I propose you the following think:

Internal versions:

-       v0.7 => 2009-03-27

-       v0.8 => 2009-05-01

-       v0.9 => 2009-07-03

First public vesion:

-       v0.99 => 2009-09-18

ð  Creation review to ask for this version.

 

Your opinion?

 

Tell me, I would like to include that in the minutes…

 

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