Re: branch-2-0

[Gary V. Vaughan]

Hi Bob!

Bob Friesenhahn wrote:
> A day or two ago you mentioned that you were going to create branch-2-0 
> sometime this weekend.  It seems that this branch was recently created. 
> All of my commits today ended up on HEAD rather than branch-2-0 since I 
> was not aware that branch-2-0 was created yet.

That's okay, I can merge them across with arch.

> What is the recommended approach toward preparing for the 2.0 release? I 
> assume that all syntax/bug fixes should be applied to branch-2-0?

Normally we don't branch until the point release, but 1.9d ended up with
some enhancements that should probably have waited until after the 
release.  Normally we are fighting with CVS, but there are public arch
mirrors of the current branches now.

From here on in, branch-2-0 should receive bug fixes only, and anything
else can go on HEAD.

> Why were we in a hurry to create branch-2-0 while libtool is known to 
> still suffer from many simple syntax issues?

Arch makes merging astoundingly easy.  If you don't want to commit 
twice, just put your fixes on branch-2-0, and I'll star-merge them back
into HEAD from time to time.  If you have time and inclination, I highly
recommend publishing an arch archive of your own... it would help us 
test and integrate one-another's changes and save the fuss of applying
patches from email attachments.

I wanted to help (myself mainly) avoid the temptation to commit 
`cleanups' to the branch that 2.0 will be released from.  Having a 
branch for 2.0 now means I can commit cleanups to HEAD (rather than 
waiting and then forgetting them) and put only fixes on the release branch.

Cheers,
        Gary.
--
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature