Andi Gutmans wrote: > > At 01:36 AM 11/14/2001 +0100, Stig S. Bakken wrote: > > > I didn't quite understand what you mean :) > > > All I said was that if you create a branch say "4.1.0" and you want to > > > release "4.1.x" from that branch later on whilst HEAD has already moved a > > > couple of months you're going to have a hard time doing it. > > > >Yes, merging bug fixes into that branch would be more difficult. But > >certainly possible, _if_ we identify a need for small bugfix releases. > > > >The point is that for the person having a problem with a bug in 4.1.0, > >upgrading to 4.2.0 may be a problem because of all the other changes. > >In this case, a 4.1.1 release containing only that bug fix would make a > >lot of sense. I've been in this situation a few times myself, and it's > >not funny (X is broken in 4.0.1, 4.0.2 fixes X but breaks Y). > > Stig, > > I understood the point from the beginning and I have no problem in trying. > I was just skeptical about how well it will work in real life.
I think it will work if we can streamline the release process so it takes a couple of weeks instead not six months. This way HEAD and the release branch won't be too different when the release is out. If we also get rid of extensions, there's even fewer potential conflicts. He who lives will see. :-) I think it's definitely worth an try. - Stig -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
