Comment 4 for bug 777824

Thanks Martin, yes that is the sort of case - but I scoped this to the just the series and used the other bug to illustrate the one project to the other.

Robert, I'm not sure I understand why you think it would interact badly with speculatively adding products. I'm thinking this is for a specific package that may apply to multiple product series (ie. Lucid, Maverick ). By setting the defaults appropriately, it will bring it to the attention of the other team (and keep it on searches for that series... ;) ) Its easy enough for that person to go in and adjust the priority or status. If they disagree it is appropriate - Confirmed -> Invalid or Won't Fix. Similarily High -> Low is an easy enough transition - after the knowledgable person looks at it.

What happens by it being created as New/Undecided, is that when its a different team person, they don't see it on their radar. ie. there is a different set of kernel developers working on SRUs as opposed to those working on development.

I can pull examples out of https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-04-15, but there is also a similar type of report that will need to be generated for SRU releases.