Re: [eigen] Bugs on bugzilla

[ Thread Index | Date Index | More Archives ]

On Fri, 13 Jun 2014, Christoph Hertzberg wrote:

For new bugs, we either need to do this on a regular basis, or we need clear responsibilities (maybe per module?).

We had people responsible for particular modules for a while, but then reverted to the current model where bugs are assigned to 'nobody' at start. I don't remember why, but one side-effect of assigning a bug to somebody is that nobody else will work on it.

In another mail, Christoph Hertzberg wrote:

Every feature request still in "NEW" state (at some deadline) gets closed due to lack of interest. The same for every bug that nobody can reproduce anymore.

I'm not sure it is ideal to close feature requests due to lack of interest. To me closed means that we are not going to do that, while a lack of interest means that it is not going to be done anytime soon but that if somebody else would do it, we would maybe incorporate it. Perhaps an INACTIVE state would reflect this better?

I could add another status "ReviewNeeded" for bugs where we have a consensus on how to fix them in general and which have a working patch attached.

There is also a possibility in bugzilla to ask for review of a patch:

It is possible to search for bugs with patches needing a review, I think. The advantage of the bugzilla system is that reviews are per-patch, not per-bug, and that they can be assigned to a specific reviewer. The disadvantage is that they do not work for pull requests via bitbucket (and that in practice it does not seem to have worked that well).

I guess we do need the "ReviewNeeded" status to support bitbucket pull requests. In that case, I think we should remove the review flag on bugzilla patches so that we do not have two systems to indicate that a patch needs review (I do not think that the more specific nature of the bugzilla system buys a lot).

We should probably update the wiki to reflect the changes to how we are using bugzilla.


Mail converted by MHonArc 2.6.19+