fix SBCL bug importances on Launchpad

[Nikodemus Siivola]

Currently we use the "Wishlist" Importance for new features. This is stupid, as it prevents us from prioritizing features here on Launchpad.

My proposed new guidelines:

- Features: tag with "feature", use a subject line starting with "wanted: ...", classify Importance according to the guidelines below.

- Bugs: tag with "bug", use a subject line starting with "bug: ...", classify importance according to the guidelines below.

- Patches addressing issues without existing Launchpad bugs. Tag with "review", use a subject line starting with "patch: ...". If the issue is a bug or a feature, also tag and classify importance accordingly. Patches that don't change behaviour but just clean things up should be tagged with "cleanup" in addition to "review", and be classified however seems best.

Setting Importance for Bugs:

Critical: We don't want a release where this isn't fixed. Typically reserved for bugs that would otherwise be classified as High, but are regressions to boot.

High: Nasty stuff like potential heap corruption, miscompilation, deadlocks, etc. Other things can classify as High if they don't have workarounds, or occur in really annoying places, etc. Things that would classify as Medium but are regressions are High.

Medium: The default. If there isn't a reason to classify it as anything else, it's Medium. Things that would classify as Low but are regressions are Medium.

Low: Esoteric edge cases, things that are clearly bugs but have been the way they are for 20 years and no-one noticed till now, things that have trivial workarounds, etc. Things that would classify as Wishlist but are regressions classify as Low.

Wishlist: Not really a bug even, but "would be nice if" -- trivial typos in documentation or error messages, etc.

Setting Importance for Features:

High: Not new a new feature, but a missing one. Something we should have had ages ago.

Medium: An important new feature. Something worth writing several blog-posts about.

Low: A notable new feature. Something worth writing a blog-post about.

Wishlist: A trivial new feature. Something worth tweeting about.

---

Why? Even if we don't fix items in order of importance, it is good to be able to signal to users how important we consider something. (For example, missing newline policies on external formats would classify as High. It's something we should have, but don't.)

[Roman Marynchak (roman-marynchak)]

I cannot change the importance of my own patches/reports (the field is inactive). I guess that only the committers can do that?

So, should I upload new patches with the Importance field value by default ("undecided")?

[Nikodemus Siivola (nikodemus)]

Only members of SBCL hackers can set importance, yes. (Can't change that, it's a Launchpad policy.)

When uploading new patches never mind the importance -- just make sure the review tag is there, and others if appropriate.

[William Halliburton (whalliburton)]

Shouldn't this make it into a file in the repo?