Improve bug association with specific Ubuntu releases

[Kate Stewart]

When a bug is generated automatically for a package, automatically "nominate" it for the release where it was found.

This will help sort the bug and help us recognize old bugs that may no longer be applicable (ie. bugs for Dapper, when release is no longer supported and package isn't in subsequent releases). By automatically nominating the bug it will more likely get focus by the release team for current development and for stable release consideration.

[Martin Pool (mbp)]

This seems related to, and perhaps solved by,
<https://dev.launchpad.net/LEP/OnlySeriesTasks> which is basically to
say that bugs will always be targeted to a distro series.

[Robert Collins (lifeless)]

Indeed. I'm going to mark this won'tfix because in our current model this would massively bloat the database with commensurate performance implications (compared to the OnlySeriesTasks approach which does not have that downside)

[Kate Stewart (kate.stewart)]

I was unable to edit. https://dev.launchpad.net/LEP/OnlySeriesTasks, and wanted to get some defaults considered for discussion. I also appear to be unable to change the status of this bug back to New.

It IS related to the goal that bugs will always be targeted to a distro series. :) I think what is being proposed from a concept is a good idea, but want to make sure its implemented in a way that makes less work for the release teams rather than more.

Problem is that we have multiple distro series "live" where different bugs can come in from- and I'd not like to see them all targetted to the "development series" when apport runs and clearly reports it as against a different Ubuntu releases.

[Jonathan Lange (jml)]

Re-opening this because there is a genuine underlying problem that needs solving. If <https://dev.launchpad.net/LEP/OnlySeriesTasks> solves it, great.

Kate, by "generated automatically", do you mean bugs generated by apport? If so, could we change apport to create the proper series link, rather than making a server-side change?

[Kate Stewart (kate.stewart)]

    Yup, I'm meaning the bugs generated by apport in particular.

We can certainly explore where it makes most sense to fix, if we can agree on how and when the task series will be created, and what the model will look like for some use cases.

[Bryce Harrington (bryce)]

Having Ubuntu bugs always targeted to a release series is a very good idea.

For manually filed bugs, I suppose there would need to be some way to let the user specify the series, and/or perhaps detect automatically based on browser version or some such?

For automated bug reports such as from apport, I believe launchpadlib provides the functionality needed to nominate them. Apport already tags by the release codename, and I think apport would be the right place for implementing series nominations as well. However note that apport can generate a LOT of bug reports...

[Robert Collins (lifeless)]

So, I think the right thing here is for apport to create series tasks today. That should be easy to do using launchpadlib. I'm going to retarget this bug onto apport, where the change needs to happen. Onlyseriestasks would make this more obvious but is orthogonal.