link / nominate bug to a Ubuntu series?

Nomination is a process that the Ubuntu bug supervisors used to suggest bugs that series drivers may want to schedule a fix for. This is most often used to suggest a back ported fix, but can also be used for series that are in development.

You are not an Ubuntu bug supervisor, you cannot nominate bugs. Before anyone can consider a bug fix for a supported series, there must be an existing fix, which does not appear to be the case for bug 482533.

You can contact Brian thomason and ask if he really intends to work on this issue, or at least comment on the bug about what he thinks needs to be done to fix it.

Thanks. Your answer begs some more questions, and my original question is still unanswered.

1) my original question was: how do I tie a bug to an Ubuntu series -- i.e. how can I say "this bug I'm reporting is for Lucid" or "this bug was reported for Karmic by someone else but also applies to Lucid"?

2) is the nomination process documented somewhere? Can we see who is a bug supervisor? In bug #482533, it says "Nominated for Karmic by U Das", but the user's profile doesn't list any memberships or anything special.

3) I actually proposed an obvious, trivial fix for bug #482533 in comment #2. What do you mean "there must be an existing fix, which does not appear to be the case..."?

I suspect the maintainer would be more willing to INCORPORATE THE OBVIOUS FIX I suggested if he realized the bug exists in Lucid too (and probably in Maverick and Natty). Or maybe not. But in any case I want to document this fact on the bug page.

1) You cannot say it affects a series, that is to say the bug is only in a series. That is for the bug supervisor to determine. This bug really is in Ubuntu, not a series. When the bug fixed in Ubuntu (the version in development), then it can be said to only effect one or more series.

2) I know of <https://wiki.ubuntu.com/RCBugTargetting>. There may be other documented used by the Ubuntu Community. In this case, there was a bug that permitted any user to nominate a bug for fixing in a series, even if there was no fix. Ubuntu's drivers then devalued nominations because users were using the process to vote, which is not the intent.

3) Attached your proposed fix and mark it as a patch. I am told that Ubuntu bug supervisors look for patches. When the fix is released, then you can comment on the bug requesting a Lucid backport.

OK. Well, I noticed that apport adds the tag "lucid" when reporting a bug from a Lucid install, so I guess that's as close as you can get to documenting your report.

Thanks Curtis!