On Tue, Dec 04, 2012 at 01:19:43AM -0500, Scott Kitterman wrote: > > Unfortunately, it was only after I copied it that I noticed that all three > of these bugs were for feature backports that don't meet SRU criteria: > > https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081388 > https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081391 > https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1081392
I'm not as deeply concerned about SRUs for non-critical issues and feature backports (*cough* SecureBoot *cough*), but I do want to see each such feature well-argued by the uploader and ACKed by the SRU team, which leads me to the next point: > Then I noticed that they were accepted into precise-proposed by someone > who is not even a member of ubuntu-sru. We have several people who have various queue and archive permissions via other teams who are expected not to operate outside the charter of the teams they're in. It's widely understood that the responsibility for SRU review falls on the SRU team, and it's a bit irksome to see updates being "slipped in" past those arm's-length agreements. While it's true that we could use some new blood in many of our privileged teams, these aren't the sorts of things where we want people just jumping in and doing the work, this should take a bit of discussion and, at time, training or guidance. Failing those steps, seeing people slipping their uploads in is pretty much a non-starter. ... Adam -- Ubuntu-release mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
