This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Auto-assign regressions (maintainers, read!)
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Giovanni Bajo <giovannibajo at libero dot it>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 25 Nov 2004 10:44:27 +0100
- Subject: Re: [RFC] Auto-assign regressions (maintainers, read!)
- References: <co397v$tju$1@sea.gmane.org>
- Reply-to: Richard Guenther <richard dot guenther at gmail dot com>
On Thu, 25 Nov 2004 01:33:02 +0100, Giovanni Bajo
<giovannibajo@libero.it> wrote:
> Hello,
>
> I'm sending this message because we were discussing the issue deep into
> another thread on the mailing list.
>
> I (and others) believe that it would be useful to automatically assign a PR
> about a regression to the author of the patch which caused/exposed the
> regression. Of course, this does not want to be a way to coerce people to
> work on something: the maintainer can just unassign the PR if he does not
> want/have time to work on that, or if he can't fix the exposed bug for some
> reason.
>
> We think this would be valuable for the bugmasters, the RM and the
> maintainters themselves. Does anybody who actually produce patches have an
> objection against this new policy? Otherwise, I'll prepare a patch to our
> bugmastering policies to make it go live in a few days.
Can't we have a caused-by-patch field in bugzilla where we could link the patch
causing the failure and a caused-by field with the author (and
automatically CC'ing
him)? I don't think it is a great idea overloading the assigned-to field.
Richard.