Hi!
> For instance, 0f180a63 was committed to 5.3 in April 7 (a
> stream_get_line() fix). It is most definitely in 5.4.4RC2:
>
> $ git merge-base 0f180a63e php-5.4.4RC2
> 0f180a63ebb2d65bbe49b68d2430639b20443e9a
>
> However, there's no mention in NEWS.
I don't see NEWS entry for 5.3 either for
Hi!
> Sorry to bring this up again, but they aren't. 5.3 NEWS are not being
> merged.
Something weird going on with the NEWS. For example, I did cleanup in
this commit:
https://github.com/php/php-src/commit/5ebb0e520f4c31d09d9e5acd323162eca3fee0e3
However I'm looking at the tree now and it's g
On 06/01/2012 12:48 AM, Gustavo Lopes wrote:
> If the RMs are unwilling to do such merging, we should change the policy to
require updating the
> NEWS files in every stable branch to which the fix was merged.
This makes sense to me.
Chris
--
christopher.jo...@oracle.com
http://twitter.com/#
