I'm not sure that's necessary. I used to tag 0.98 RCs with 'svn copy' and then commit version changes, changes.txt, doc updates, etc on top of the tag, then check out the result (in svn a tag is a branch is a tag), build it, test it, and release it.
With git the process could be very similar. Take your tracking branch, make the release-ish updates, commit them (you can "squash" multiple local steps with git commit -a --amend), but to the local tracking branch only. When you have all of the changes in place as a commit ready to go upstream, try a push. If someone else has pushed first upstream, your push of the combined release-ish changes will fail. Rebase your local release changes (git fetch upstream && git rebase --ignore-date upstream/branch, update changes.txt, git commit -a --amend) try again. Your commit of all of the release changes will be atomic in this respect. It does mean that in rare cases you might have to accept an unexpected commit into your RC, but our branch commit frequency is few per day so that is unlikely. On Thu, May 22, 2014 at 11:45 PM, lars hofhansl <[email protected]> wrote: > Yeah, I will do that for now. > Means we're back to the no-checkins-for-a-bit-please times, though. > > > > ________________________________ > From: Stack <[email protected]> > To: HBase Dev List <[email protected]>; lars hofhansl <[email protected] > > > Sent: Thursday, May 22, 2014 11:12 PM > Subject: Re: 0.94.20RC0 tonight... > > > Can you not take the 0.94 jenkins build? If no changes, its same as the > tag? > St.Ack > > > > On Thu, May 22, 2014 at 9:57 PM, lars hofhansl <[email protected]> wrote: > > > Looks like git is getting in the way of productivity again... > > > > > > Does anybody know how to do a jenkins build against a specific tag? > > > > The "obvious" way of specifying */tags/<tagname> in "branch" field does > > not work. > > Helpfully, the git plugin for jenkins does not report any error (that > > would be too old school, I guess). Rather the build just hangs. > > > > So has anybody does this successfully? If so, how? > > > > > > -- Lars > > > > > > > > ________________________________ > > From: lars hofhansl <[email protected]> > > To: Hbase-dev <[email protected]> > > Sent: Thursday, May 22, 2014 3:54 PM > > Subject: 0.94.20RC0 tonight... > > > > > > ... if I can work out the git process. > > > > -- Lars > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
