Re: Re: Proposal for release process (Was: Re:[PHP-DEV]4.1.0)
| From: | Andi Gutmans | Date: | Wed, 14 Nov 2001 05:03:29 +0000 |
| Subject: | Re: Re: Proposal for release process (Was: Re:[PHP-DEV]4.1.0) | ||
| References: | 1 2 3 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-70405@lists.php.net to get a copy of this message | ||
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. Andi