Package sponsorships involve awkward bugtracker machinations
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The processes for handling Ubuntu package sponsorships are described in <https:/
* a "requestsponsor" shell script that reports a bug on your behalf
* unsubscribing teams from bug reports
* setting a bug report to Incomplete if the attached patch needs work, even if the bug itself is fully described
* several steps where multiple things (importance, status, tags) need to be changed at once.
<persia> Vorian: Please unassign yourself when submitting bugs to the UUS queue.
* Fujitsu finds that part of the process to be silly, but necessary due to Launchpad's lack of a good workflow for sponsorship.
* persia agrees with Fujitsu
<Fujitsu> We shouldn't really have to hack sponsorship processing into the existing task.
In the long term this will be fixed by <https:/
<persia> mpt: OK. If we're looking at something to be implemented in the 6-12 month timeframe, I'd hope our volume would reach the point that we're ready to properly review an interface. Right now we're only at around 10-20 sponsorships a day, which isn't impossible.
| description: | updated |
| description: | updated |
| Thierry Carrez (ttx) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
It's not only a complex process, it also causes tracking issues (difficult to tell which bugs have a fix proposed without a subscription cross-check).
Part of the solution would be to have a "Fix proposed" status that would sit after "In progress" and before "Fix committed". Incomplete patches would be brought back to "In progress" rather than "Incomplete".