Code doesn't grow old. There's really no reason not to release 4.1.0, and start the 4.2.0 releasing immediately afterwards. Mixing the fact we're stressed to put out a released (due to the $_GET&friends feature) and the fact that we have several big changes in key features (sessions, file uploads) is a 'clear and present danger', in my opinion. We should be able to take our time with it, if necessary.
Zeev At 20:54 12/11/2001, James Moore wrote: > > > > i haven't really changed my mind - but i want a fast > > decision. as there isn't any clear consens here i think we > > should release 4.1 as-it-is-with-the-last-showstoppers-fixed > > and go from there. we should also learn from this and assign > > a RM for the next release! i mean a real release-master... > >Putting out a release we arnt happy with is worse than not putting a release >out at all. >Lets restart the cycle and take care this time.. 4.1.x is asking for trouble >coming from a branch as old as the 4_0_7 branch is..lets rebranch from HEAD >and really push the release we could probably get it out in 1.5 - 2 weeks. > >- James > > >-- >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] -- 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]
