Unnecessary, you can tell the user within the closing comment
in which branches you fixed the bug. Don't forget that it can
CHANGE later, someone reverts the fix or the fix wasn't needed
or.. you get the picture.
--Jani
On Thu, 13 Oct 2005, Lukas Smith wrote:
Hi,
some of you may be aware of the wiki I set up to manage/document the todo
lists and parts of the release management for PHP releases. In response to
this Wez created a set of patches to enable developers to set milestones (aka
PHP versions) for bug reports. While I do not think this replaces the need for
the wiki (which is maintained independent of php.net ressources anyways),
which is way more flexible, I think its a very good addition.
For example we currently mark things as "fixed in CVS" even if things will
never be fixed in the branch for which the user filed the bug report (like
with the streams API). Therefore I think its a very important tool to let
users know when things will get fixed. I could see the same kinds of things
happen with unicode issues being reported in the 5.x branch but only getting
addressed in php 6.x.
Anyways I think it would be a good idea to add this feature again along with
the ability to filter by milestones on the "advanced search" page. I think
this would make the life of our RMs alot easier as well.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
