This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: 4.2 Backport fix for PR libfortran/31196
On Apr 16, 2007, at 4:03 PM, Paul Brook wrote:
Where do you suggest the SC find these additional maintainers?
For my area, they could ask me. I'd be happy to point one or two
additional people out. Darwin has lost yet another person, so we're
down to just 2. So far, this isn't causing us to twist in the wind,
but, personally, I'd rather have at least three. For other areas,
first crack should go to the current maintainers to suggest people,
failing that, I'd recommend the people that have the best patches in
that area, failing that, putting out a request for people to step
forward.
Look a fortran, for a long time, there was just one person. Then
there was none, did the world collapse, no, but a bunch of people
stepped forward and to me (on the outside), it feels like they're
doing a good job.
I think that all open bug reports should be assigned to a maintainer.
For areas with multiple maintainers (i.e. most of the compiler),
how do we pick which maintainer to assign to?
I avoided trying to give an answer to this problem as the exact
mechanism doesn't matter much and any that I tried to suggest would
be controversial as there are other equally good ones that would
probably work as well. Let Andrew pick. How's that for
controversial. I think that might well be better than status-quo.
Let the RM pick. Less controversial, but, more stress on the RM,
which I'd hate to do. If the fix is identified down to a pass, pick
the person that maintains the pass, if down to a file, the person
that maintains the file. Another thought, the person listed first.
Let us define the person listed first as the bug dispatcher for that
area. Let them farm out as necessary. Or, maybe we just ask for a
volunteer. Again, the exact mechanism doesn't matter.