Why release a RC for a software that has some known bugs not fixed. This leads to a RC1, RC2, RC3 and so on. If you only want to fix thw windows bugs you stated, a 4.2.3 would be useless to me, in this case I vote against a 4.2.3 as this would delay 4.3.0 just a little bit more.
> From: Zeev Suraski [mailto:[EMAIL PROTECTED]] > > I'd really like to avoid waiting this time, though (the enemy of good is > better...). Even if we release 4.2.3 as it is in the branch, without any > further fixes, it's significantly better than 4.2.2. > > Translating this into action - my personal preference is to > release the RC > as early as tomorrow. > > Zeev > > At 16:20 17/08/2002, Dan Kalowsky wrote: > >Hrm, well a lot of the fixes I've been doing have only gone to head > >because the belief of no 4.2.3. > > > >There are still a few outstanding bugs I'd like to see fixed > before things > >we RC. Sfox and I (mostly her though) have been looking at the dbm_* > >functionality on Windows. We're questioning if it ever worked at all. > > > >I can run through a list if there is a desire to see one. > > > >On Sat, 17 Aug 2002, Zeev Suraski wrote: > > > > > I'd like to raise the option of releasing 4.2.3 again. I > believe that it > > > would be quite a while before 4.3.0 is out, and there are > quite a few fixes > > > in the 4.2 branch that should make the userbase as soon as possible, > > > especially the Windows userbase. > > > I think that releasing 4.2.3 can be done within approximately > one week, > > > with one RC, barring unexpected surprises. > > > Opinions? Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
