This is why other Eclipse projects cap their maintenance streams when the next release is published. We should now do the same.
Adding 0.0.100 to every bundle proactively to the release means that all bundles appear to have updates, even if they never actually get any real changes during the development of the release. That’s not why we have a versioning scheme. The point of versioning is so that new binaries don’t need to be downloaded and installed by the updater if there are no changes in some bundle.
On 7 July, 2016 at 10:22:43, Ed Willink (ed@xxxxxxxxxxxxx) wrote:
Hi
Even a bug fix requires +0.0.1, which is easy if a pro-active
+0.0.100 has already been done by the successor. It's not possible
at e.g. 'Neon.3' if the Oxygen.0 successor has already re-released
at +0.0.0.
Regards
Ed Willink
On 07/07/2016 16:02, Christian Damus wrote:
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?
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
![Avast logo]() |
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
_______________________________________________
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
![Avast logo]() |
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
|
