Community
Participate
Working Groups
Created attachment 228777 [details] patch.rt.equinox.bundles.R3_8_maintenance To be applied right after I20130326-0800
Created attachment 228778 [details] patch.rt.equinox.framework.R3_8_maintenance
Created attachment 228801 [details] patch.rt.equinox.bundles.master
Created attachment 228802 [details] patch.rt.equinox.framework.master
(In reply to comment #0) > Created attachment 228777 [details] > patch.rt.equinox.bundles.R3_8_maintenance > > To be applied right after I20130326-0800 Did you mean for this comment to be for the patches against master? or for all 4 patches?
I see we have moved the version to be 4.2.2 (for Juno maint) and 4.3.0 (for Kepler). I still am unsure how these versions get used in the whole maven artifact world, but does this make the most sense for Equinox? Technically Equinox Juno is 3.8.x and Equinox Kepler is 3.9.x. Now with that said I think these release version numbers are really not that important and are more marketing than anything else. So if we think it will be less confusing to just move Equinox release version numbers up to be in sync with the Eclipse project marketing version then I would not complain too much ;-) But I want to make sure this was not just an oversite when Paul produced the patches. And I thank you very much for doing so Paul!
(In reply to comment #4) > > Did you mean for this comment to be for the patches against master? or for > all 4 patches? For all 4 patches. (In reply to comment #5) > I still am unsure how these versions get used in the whole maven artifact > world, but does this make the most sense for Equinox? Technically Equinox > Juno is 3.8.x and Equinox Kepler is 3.9.x. In most places in platform we picked 4.3 as the next release number, just because that's what we say we're building, and I think most components just did that as well instead of picking 3.9 ... but that's totally up to the components, and wouldn't effect the build anyway. In the build case case, the parent versions are related to the "stream" we are building. It would be technically possible to have the eclipse parent at 4.3.0 and have the rt.equinox.framework/pom.xml at 3.9.0, as long as someone insures that all references to any parent match the version that publishes the parent (but that sounds like even more work :-) For building 4.2.2+ the parents match, for building 3.8.2+ we believe we'll just use the 4.2.2 eclipse-platform-parent with some URLs replaced by properties (since there are a number of repos that provide one branch to both maintenance builds, and there's no point in branching them just to manage some poms). > > But I want to make sure this was not just an oversite when Paul produced the > patches. And I thank you very much for doing so Paul! Yeah, it looks a little strange, but the strangeness will fade when we get away from 2 maintenance branches. PW
rt.equinox.framework master: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/?id=7f2a6a87ae21c4a562d836d969207c2177c24368 rt.equinox.framework R3_8_maintenance: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/?h=R3_8_maintenance&id=a6e5a0616d641f6a00ccc2ed4ccdc989b010d130 rt.equinox.bundles master: http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?id=8b767d47756ce793565a884c3e0ae894f5609a63 rt.equinox.bundles R3_8_maintenance: http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/commit/?h=R3_8_maintenance&id=e65e1c02716fb8965e849ada430c3bc70da24061
Thanks Paul! I released the patches.
(In reply to comment #7) > rt.equinox.framework master: > > http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/ > ?id=7f2a6a87ae21c4a562d836d969207c2177c24368 > This is the wrong commit. Apparently I did not push up my commit. It is there now: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/?id=40c6d3d3a5ba90d2a63d60d6453bb3f0ed37d4be
