Pierre, It has everything to do with the separate branch. Our current approach, (as flawed as it maybe) ensures patches are not missed, since there is no separate branch, so patches go into the release tree. With the new approach if something is not merged it is not part of the release. This also makes it confusing for the users, since the dev fixing the bug indicates on the bug tracker the issue was resolved, and will be part of the next release. And then the next release comes out and the bug/issue is still there...
On 2009-12-07, at 9:55 AM, Pierre Joye wrote: > 2009/12/7 Ilia Alshanetsky <i...@prohost.org>: > >> The NEWS file would tell me why patches were not merged? Also the news file >> does not contain entries about many fixes that don't have corresponding bug >> # attached to them. >> As I recall the 5.3.1 NEWS entry were merged back to the PHP_5_3 6 days >> after the release by you ;-). > > Ok, so what you are arguing about is that you don't know why something > was not merged. That's something we like to improve but it has nothing > to do with the extra branch, absolutely nothing. > > Cheers, > -- > Pierre > > http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
