+1 (on the -0). I think we should stop everything else until 1.0 is out .. after all, this *1.0*. As I said to Tom during the WS-DEsc F2F, "you only get one chance to make a first impression" .. screwing up 1.0 because of working on stuff post 1.0 is silly.
Sanjiva. ----- Original Message ----- From: "Tom Jordahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 24, 2002 9:21 PM Subject: RE: [VOTE] Re: managing change during the 1.0 release process > > I am -0 on this. > > I don't think we need a branch, we need to all fix the 1.0 targeted bugs and release 1.0. :-) > > -- > Tom Jordahl > Macromedia Server Development > > > > -----Original Message----- > From: Glyn Normington [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 24, 2002 3:48 AM > To: [EMAIL PROTECTED] > Subject: [VOTE] Re: managing change during the 1.0 release process > > > I agree with Sanjiva. In fact I'd go further and say that the RC's should > be on a branch which will ultimately end in 1.0 (or eventually 1.0.n). > Compare how Mozilla managed their releases at > http://www.mozilla.org/roadmap.html. Of course Axis is tiny compared to > Mozilla, but why not copy a process which seems to work well? > > So, let's put this to the vote: "create a branch for 1.0 and allow only > agreed changes to be committed to that branch". > > Here's my +1. > > Glyn
