Re: Web: Making GNATS fixes a release criterion

["Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>]

> Good, thanks!  Is there any way to actually prevent people from
> entering high-priority bugs, or is simply notifying people that
> they're not supposed to do this the best we can do?  For example, can
> we make gccbug.el not allow high as a valid priority?  Or make the
> server disallow these entries from non-maintainers?

The way I envision this is that "normal" people will only enter "open"
reports. If you see a report that has been "analyzed", it must have
been a maintainer that did so. This is almost reliably enforced since
the submitting procedures don't offer entering a state, so all new
reports come in the "open" state. There is actually a way around that,
and I can tell you in private how that would work :-)

So if an open report has high priority, the priority was given
incorrectly by a non-maintainer; the maintainer analyzing the report
will have to decide whether the report really deserves being high
priority.

If that procedure is not sufficient, I can investigate how to make it
safer. It seems that that kind of access control is not supported by
gnatsd, at the moment.

Regards,
Martin