Hi, Rémi,
Yes, this is a very good point.
We could start with 2.2 version on the master branch. Because the Oxygen stream is continuing in parallel with Neon.x and, in fact, makes its first release after Neon.x is closed, we can bump the version numbers along on Oxygen as we go.
So, for example, at this point we would have org.eclipse.papyrus.uml.service.types at 2.1.0 on Neon.x and 2.2.0 on master. After Neon.1 is released, if we then need to make a 2.2.0 in Neon.2, at that point we bump master to 2.3 to stay ahead. It doesn’t actually matter what the versions on the master branch are until that branch releases.
In any case, I don’t think we can set Oxygen/master at 3.0 until we know there will be breaking API changes, because this has a definite impact on applications that extend Papyrus and how they must manage their own updates.
cW
On 7 July, 2016 at 09:24:29, SCHNEKENBURGER Remi 211865 (remi.schnekenburger@xxxxxx) wrote:
Hi,
Reading
https://wiki.eclipse.org/Version_Numbering#When_to_change_the_minor_segment, it seems that it should be 2.1.0 on maintenance branch for Neon.1, and it should become at least 2.2.0 for Oxygen.0.
“Also, when the minor segment is incremented in a maintenance
stream, you must increment the minor segment again in the next stream. For example, if plug-in P has version 2.2.7 in the 1.0 product release, it would increment to 2.3.0 in the 1.0.1 product release, and 2.4.0 in the 1.1 product release. Incrementing the
minor segment in a maintenance release after there has been a release in a future stream cannot be done unless you have left a gap in your version numbers to leave room for it.”
However, when I read the last sentence, it seems that we should leave more space for Neon.2 & Neon.3? If yes, the scheme should be:
Neon.0: 2.0.0
Neon.1: 2.1.0
Neon.2: space left in case of 2.2.0
Neon.3: space left in case of 2.3.0
Oxygen.0: 2.4.0? or even directly 3.0.0?
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
 www.eclipse.org/papyrus
How will the minor version be increased on the maintenance branch? If the version is 2.1.0 on both branches, they will look like the same version, even though one was compiled
against Neon dependencies and the other Oxygen dependencies.
Or will the versions be 2.1.1 on the Neon stream and 2.1.100 on Oxygen?
Or does it not matter? Maybe I’m over-thinking it ...
On 7 July, 2016 at 09:01:46, TESSIER Patrick 202707 (patrick.tessier@xxxxxx) wrote:
Hi,
Because of this gerrit :
https://git.eclipse.org/r/#/c/76697/1,
I inform that I will increase the number of minor version of uml service type for the version neon and oxygen.
Patrick Tessier
+33 (0) 1 69 08 48 63
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
DILS/Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE),
Point Courrier n°174
91 191 Gif sur Yvette CEDEX
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
