[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [papyrus-rt-dev] Version numbers
|
Thanks, Ernesto, for the link.
Reading the Eclipse rules, we should not even have a 1.0.1 as an option at this point as we do not yet have to ship any fix on 1.0.
Also, when we moved from Mars to Neon in the 0.7.2 revision, we should have stayed on 0.7.2 for Mars and moved to 0.7.100 for Neon. A fix required on 0.7.2 would then have seen a change in version to 0.7.3. Changes for Oxygen done now would be on done with versions 0.7.200 and up.
So if we want to align, we would change our Neon version to be 0.7.100. When we are ready for release, everything will go to 1.0.
I assume here that the 4th field would continue to be automagically created by the build system from thee date/time of the build.
/Charles
On two different threads the topic of version numbers has come up. We got stuck with 0.7.2 even as we added functionality and all kinds of updates. Furthermore, in bugzilla we had a version 0.8 which was never used, and we are using 1.0.1 for everything that is planned for later.
None of this seems to align with the Eclipse policy [1]. Perhaps we should start to follow that a bit more closely before things get too messy? In particular, I'm not fond of putting everything under 1.0.1. It would seem to me that new features that don't break existing functionality should go into 1.1, 1.2, etc. while bug fixes would go to 1.0.1, 1.0.2, etc., no?
Also, I'm not sure what is the proper way to handle versioning of individual plugins. So far we have had everything with the same tag "0.7.2", but we are continuously publishing nightly updates with bug fixes. Should individual plugins advance their "service" number independently, or would that become very difficult to handle, particularly for POMs?
-- Ernesto Posse Zeligsoft
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
