|Today's clone of the -b I_4_3 question [message #1092409]
||Thu, 22 August 2013 19:12
Registered: July 2009
I just did a git clone using "-b I_4_3" as noted in other forum posts as the branch to use; for example:|
git clone -b I_4_3 http://git.eclipse.org/gitroot/stardust/org.eclipse.stardust.build.tools.git build.tools
When I do that I notice that it appears there have been changes for the SR1 RC1 release. For example in product/product-parent/pom.xml I see changes like:
among other changes.
Should this change have be made to the I_4_3 tagged sources? Isn't that tag meant to match released sources?
I found the complete set of changes at http://git.eclipse.org/c/stardust/org.eclipse.stardust.build.tools.git/commit/?h=I_4_3
This is not how I would typically image branching be used. What is the scheme being employed? Should we still be using the I_4_3 branch as the branch to be integrating with the 4.3 Kepler release code?
It appears that you are using I_4_3 as the integration branch is there some other tag we should be using for the stable code base that matches the initial 1.0 release?
Is this still too bleeding edge to be used by the general community?
Powered by FUDForum
. Page generated in 0.08361 seconds