Going through the PHP 5 Bug Summary Report looking for stuff I may be able
to help out with and finding a lot of them that are fixed in current cvs but
are still marked as open. I'm curious when you determine a bug to be fixed
and mark it as such. I imagine a few of these are only fixed in 5.1 cvs tree
(which is what I'm testing against), do you wait for 5.1 release to mark
them as fixed?
I've been commenting them as fixed in 5.1 CVS (hope you don't mind) when I
run across them and verify expected functionality.
Bob
At 05:23 PM 10/12/2004 -0700, Robert Silva wrote:
Going through the PHP 5 Bug Summary Report looking for stuff I may be able
to help out with and finding a lot of them that are fixed in current cvs but
are still marked as open. I'm curious when you determine a bug to be fixed
and mark it as such. I imagine a few of these are only fixed in 5.1 cvs tree
(which is what I'm testing against), do you wait for 5.1 release to mark
them as fixed?I've been commenting them as fixed in 5.1 CVS (hope you don't mind) when I
run across them and verify expected functionality.
We usually mark it as Fixed in CVS. I guess it's not obvious which CVS
(4.3.x, 5.0.x, 5.1.x) so you might want to add that with a text comment.
Andi
Going through the PHP 5 Bug Summary Report looking for stuff I may be able
to help out with and finding a lot of them that are fixed in current cvs but
are still marked as open. I'm curious when you determine a bug to be fixed
and mark it as such. I imagine a few of these are only fixed in 5.1 cvs tree
(which is what I'm testing against), do you wait for 5.1 release to mark
them as fixed?
As soon as they are fixed in CVS we mark the bug as "Fixed in CVS" in
the bug system, and optionally add a comment for which version it is
fixed.
I've been commenting them as fixed in 5.1 CVS (hope you don't mind) when I
run across them and verify expected functionality.
Not at all, more people is good.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org