tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: Bug workflow
Date Thu, 17 Sep 2009 18:04:53 GMT
Uwe G√ľnther wrote:
> So I could set this one to resolved! Thanks Tim.

Thank you. Help closing bugs is always much appreciated.

> Some other questions are popping up in my head right now:
> 
> - How do you guys to choose which bugs to fix first?
As we say at the ASF - you scratch you own itch. We don't have a
community wide priority - each developer will prioritise them their own
my. My personal priority list is something like:
- security bugs (handled on a private list)
- regressions
- things I (or my employer*) care about
- oldest open 5.5.x or 6.0.x bug without a patch
- enhancements

* This only applies during work hours :)

There are, of course, some exceptions to my rules:
- A bug/enhancement with a patch and a good explanation (or better yet a
test case, including source code, that runs without any hassle) is
likely to get committed as soon as I see it.
- I am trying to balance bug fixing and Servlet 3 development so doing a
bit of each

> - If you pick up a bug for fixing, do you flag that up
>   somewhere in Bugzilla?

Normally no. Mainly, I think, because we rarely get clashes. Most bugs
don't take that long to fix so the likelihood of clashes is small. As
the number of open bugs decreases (there are now less than 50 open bugs
against tc5 and tc6 without patches) the chances of a clash increase.
I'd suggest if you find yourself spending more than an hour on a bug it
is worth noting it. I'd also suggest you include a rough time frame for
when you expect to have an update so other folks can tell if a bug is
being worked on or not.

Mark




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message