As a matter of fact I think it would be good idea to go for 4.3.1 in
February because number of bugfixes in PHP_4_3 branch is already significant
and since no major new features have been added there the QA process
shouldn't take that long either.
And I have a pretty bad bug I'm still trying to repro (just got access to a box with the bug) that needs to get into a 4.3.1.
There were some, for example Sascha's addition. This alone would qualify a full QA, and not a short and fast one. Our general idea was to NOT add new code to release branches, but at the moment developers are still doing this because *they* need a new function and dont want to wait for 5.0.0. I can understand that they dont want to wait for PHP 5, but what I dont understand is that they think less about the general stability and QA processes for the PHP 4.3.x series.
Derick
And thus the need to have a pure 4_3 tree that 4_3_1 can be branched from. Those people who need to add new features can do so on 4_3_head, but they might not ever make it into an official 4.x release depending on QA and the time cycle for 5.
Shane