On 25 Jan 2009, at 16:12, David Zülke wrote:
Am 25.01.2009 um 14:29 schrieb Lukas Kahwe Smith:
On 24.01.2009, at 17:40, Ilia Alshanetsky wrote:
I think our bug current tracker is pretty good and most
importantly makes it easy to report and update bugs which is
conducive to more issues being reported. Often extra features of
bug trackers make them overly complex to use and people just get
frustrated with them and don't report bugs as the result.
Personally I think it would be nice to have some sort of milestone
support. I think we already had that for a brief moment. I think it
would make the bug tracker a very useful tool to see when something
will be fixed and more importantly also for historical reasons.
Then again we often shuffle around fixes from one branch to
another .. so the trick is to make it possible prevent things to
get out of whack. Maybe the bug tracker should be our interface to
the NEWS file .. then again in order to be that, the solution would
need to be super duper rock solid. But it could make the life of
the RM's a lot easier.
Absolutely. Also, a "fix version" would be really good, so people
can know when a bug was fixed.
Also, CVS/SVN post-commit hooks would be nice, so the tickets are
annotated with links to the changesets. Right now, if I see
someone's comment "Fixed in CVS HEAD and PHP_5_3", I need to look at
the date, then go to the cvs mailing list or logs and find the
respective commit. Cumbersome.
If the bug number is in the commit message and we're using subversion
then there is no reason we can't add a reference to the revision in
the bug.
Scott
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
