OK, I see - I think. So when we want to produce 2.1.1 we create another branch (and tag)?
BTW, should this one be called 2.1.0 ? S. On 7/12/05, Michael Stover <[EMAIL PROTECTED]> wrote: > The point of the branch is to assist with a feature freeze for the > release, without interfering with anyone's desire to continue on with > new work. Right now, if we are ready for a release candidate, we are > ready for a feature freeze for 2.1, leaving HEAD free for new work. 2.1 > would just be for bug fixes, essentially. > > I'm going to go ahead and make the branch unless I hear back not to. > I'll wait though, give y'all time to respond to this. > > -Mike > > On Tue, 2005-07-12 at 17:21 +0100, sebb wrote: > > There'll always be some more bits to tweak, but I think the codebase > > is now OK for a release candidate. > > > > Just wondering if creating the branch should not wait until the RC has > > been tested? > > > > I.e. create a 2.1RC1 tag, build and release RC1. > > > > If that's all OK, then create the 2.1 tag and branch. > > > > Or is that unnecessary? > > > > S. > > On 7/12/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > Hey Sebb, > > > Pete's ready for 2.1 to branch - are you? > > > > > > -Mike > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
