Making GNATS fixes a release criterion

[Martin v. Loewis]

Hi Mark,

Given that GCC bug reports are collected in GNATS now, I'd like to
propose that bug classification is used to determine release of GCC as
well. The GNATS documentation proposes

`>Priority:'
     (ENUMERATED) How soon the originator requires a solution.  Accepted
     values include:

    `high'
          A solution is needed as soon as possible.

    `medium'
          The problem should be solved in the next release.

    `low'
          The problem should be solved in a future release.

     The default value is `medium'.

Now, given the large number of "medium" priority bug reports, it may
not be feasible to have them all resolved. However, I'd like to
propose that at least all high-priority bugs are fixed in GCC 3. There
are, of course, two different ways to achieve that: Either a bug could
be fixed, or reclassified to a lower priority, at the discretion of
the maintainers.

FYI, at the moment, there are 11 high-priority PRs.

Regards,
Martin