Hi! > So in the end, a solution is wanted. I don't think any opinion is > allowed to be ignored for such a topic. So options > > a) release on 26th including all known bug fixes > b) do RC8, assume there are no bugs, so target 10th for RTM > c) do RC8, release on 3rd, expect there are no bugs come in > d) continue issuing release candidates till it's stable enough (needs > definition of stable and probably an RFC) > > I would really ask to reach a consent on either a) or c). IMO, the options b) and d) are the direct road to curbing 7.0.0. There is no hurry to release just to release, but it is definitely harmful to slow down the rise.
I like option c. The count bug looks like it could break a bunch of apps, so releasing with it is possible but not ideal. Since we have a fix for it I'd just wait another week. Not releasing on holiday is also a plus in my book (not enough by itself to wait another week but in conjunction with the actual serious bug in my opinion it tips the scale). P.S. of course I also assume if somebody discovers huge bug before the 3rd we'd have to reconsider, but otherwise we should assume RC8 is the future GA tag. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
