Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mmt-dev] [ATL] Version numbers

No code changes since 3.3.1RC3. However, things have changed since the 3.3.0 release, but I suppose that was addressed in your versioning already.

According to the versioning rules Ed mentioned, I should have bumped the service segment by 100 for the bug fixes in the org.eclipse.m2m.atl.emftvm plug-in (i.e. 3.3.100). Also, org.eclipse.m2m.atl.emftvm.tests should be bumped by 100. That's for the HEAD branch. R3_3_maintenance should be at 3.3.1, provided my changes to HEAD since 3.3.0 release were backported to R3_3_maintenance?

To summarise the situation:
- I haven't touched any version numbers yet.
- I have only committed to HEAD so far.


Op 17-09-12 09:09, William Piers schreef:
Hi Dennis,

Usually I change all the version numbers but it will be ok if nothing changed since the 3.3.0 release.
Note that 3.3.x releases are build against the R3_3_maintenance branch, where for instance /org.eclipse.atl/releng/org.eclipse.m2m.atl.releng.parent/pom.xml is at version 3.3.1.
Maybe you were looking at the master branch, where Ids are still at 3.3.0. They will change soon to 3.4.0 for Kepler.

I don't plan to rebuild a 3.3.1RC4 (I will just rename the current RC3 build) but let me know I you need it, before the end of the day if possible.

Best regards,


Le 16/09/2012 22:16, Dennis Wagelaar a écrit :
Hello William,

I saw there's an RC release for ATL 3.3.1, but many plugin/POM versions are
still at 3.3.0 (including the root POM). What's the policy here? Should I
update everything to 3.3.1? Or only update if there are changes since the
3.3.0 release?

Kind regards,

mmt-dev mailing list

Dennis Wagelaar
E-mail:   dwagelaar@xxxxxxxxx
Mobile:   +32 486 682357
Skype:    dwagelaar

Back to the top