| Re: [mdt-papyrus.dev] increase for minor change |
|
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 De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus Hi, Patrick, 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 ... Cheers, Christian On 7 July, 2016 at 09:01:46, TESSIER Patrick 202707 (patrick.tessier@xxxxxx) wrote:
|
