Re: [mdt-papyrus.dev] increase for minor change

[SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx>]

+1, we don’t have currently the policy to push new features/APIs in the maintenance branch once the new stream  is published. In a theoretical world, It would be possible, but not currently on Papyrus project. So there is no need to take this case into account (yet)

 

If I read correctly the chapter on segment version number, +0.0.100 shall be done only as soon as we fix something in the plugin, not automatically. Otherwise, I suppose we don’t have the possibility to reuse existing binaries if nothing has changed.

 

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

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : jeudi 7 juillet 2016 16:03
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] increase for minor change

 

After Oxygen.0 release is published, I see no reason why Papyrus would make any more API changes on the Neon.x maintenance branch.  This branch can then switch into a pure bug-fix mode.  After Oxygen.0 release, any consumer that needs further API changes should just pick up Oxygen and its subsequent maintenance releases, no?

 

cW

 

On 7 July, 2016 at 09:59:46, Ed Willink (ed@xxxxxxxxxxxxx) wrote:

Hi

On 07/07/2016 15:49, Christian Damus wrote:

Hi, Rémi,

 

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.

This doesn't work. You must bump the version before Oxygen, otherwise you may have nowhere to go for plugins that get their first Neon.x maintenance after Oxygen.0.

The problems go away if you proactively add +0.0.100 all round immediately after any release, then lazily add 0.1.0 when the first actual change occurs.

    Regards

        Ed Willink

---

This email has been checked for viruses by Avast antivirus software. www.avast.com

_______________________________________________
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