At 16:41 17/08/2002, Sebastian Nohn wrote: >Why release a RC for a software that has some known bugs not fixed.
PHP x.y.z has known bugs that are not fixed, for any given x, y and z, since forever, and until the of time. Realize that, and decisions become much simpler. Releasing a new version makes sense if it's *significantly better* than the previous version. It doesn't have to be perfect. You basically have to weight the gain (the bugs that were fixed, the fact that the semi-major version alternative is likely to be much buggier than a minirelease such as this), versus the price (QA time, possibility of introducing new bugs). If the price appears to be reasonable for the gain, you go for it. Releasing 4.2.3 the way I suggest it will not delay 4.3.0 in any way. Forgive me if I'm wrong, but I don't think anything is happening at all with the 4.3.0 release process anyway. What I'm suggesting is to let users have a significantly better version to use within one week. Nothing more, nothing less. Zeev -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
