+1 on branching for ApacheCon. I agree with Rotan, and since we just voted that this _is_ a release (albeit a pre v1.0).. :).
Re: timing, I would like to see the petstore checked in before branching, since that's a key missing element of the release. > -----Original Message----- > From: Rotan Hanrahan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 19, 2004 1:29 PM > To: Beehive Developers > Subject: RE: [Proposal] Branch for ApacheCon release? > > 0 > > If it's a release, it deserves a branch, preferably at a > point of maximum stability. > > If it's a snapshot demo, I'm not so sure it deserves a branch > unless impending activity is potentially introducing > temporary instability that would threaten the viability of the demo. > > As I've been distracted by W3C work the past few weeks, I > can't give an objective answer to the proposal. (Hence the 0.) > > ---Rotan > > -----Original Message----- > From: Heather Stephens [mailto:[EMAIL PROTECTED] > Sent: Tue 19/10/2004 20:54 > To: Beehive Developers > Cc: > Subject: [Proposal] Branch for ApacheCon release? > > > > Should we branch for our ApacheCon release? > Obviously this would allow feature work to go on in the > mainline while > we wrap up the demo polish details in the branch for ApacheCon. > > If we do want to branch does anybody want to propose a > day for it? > Perhaps early next week sometime? > > > >
