Bug triage for 2.72 release commencing

This morning I'm going to triage all the bugs in Savannah for whether
they need to be fixed before the 2.72 release.  There will be a brief
flood of bug-related email.

I will be using the "priority" field in Savannah to categorize the bugs.
Here is a summary of the codes I'm using.  (I have also put this into
Savannah itself.)

1 - Blocked: We cannot proceed with work on this bug until something not
    under our control happens, such as the submitter providing additional
    information, or a change being made to a different piece of software.

2 - Eventually: We want to fix this bug eventually but we are not going
    to commit to any particular timeline. Bugs in this category probably
    require a great deal of work which no one has volunteered to do.

3 - Release N+1: This bug is not scheduled to be fixed in the very next
    release, but we intend to get it done for the release after that.

4: do not use

5 - Unprioritized: This bug is new and nobody has looked at it yet.

6: do not use

7 - Release N (Desirable): This bug is scheduled to be fixed in the very
    next release, but it might get bumped to the release after that if we
    run out of time.

8 - Release N (Blocker): This bug *will* be fixed in the very next
    release, even if that means we have to delay the release until we're
    sure it's fixed.

9 - Hotfix: We need to put out a release as soon as possible just
    because of this bug.

zw