Hi Jamie,

On Mon, Oct 15, 2012 at 03:09:31PM -0500, Jamie Strandboge wrote:
> Note, queue not going down as much as it could be because I saw a lot of
> things (correctly) being deferred to R

I think we really need to come up with a better way of systematically
deferring sponsorship queue items that doesn't involve individual sponsors
taking responsibility for revisiting an item when the next release opens. 
That workflow tends to make developers very reluctant to move stuff out of
the queue because they can't commit to being the one to do that work in $x
weeks.  I'd really like us to be able to have a central sponsorship deferral
tag that we can batch process at the opening of the next release, so that we
can deal with this more efficiently across the team.

>  * LP: 1010433 - bash*.deb is missing "Multi-Arch: foreign" - NAK for
>    several problems with changelog file (notably, the description was
>    way too terse)
>  * LP: 1010449 - sed*.deb is missing "Multi-Arch: foreign"  - NAK for
>    several problems with changelog file (notably, the description was
>    way too terse)
>  * LP: 1010448 - grep*.deb is missing "Multi-Arch: foreign" - NAK for
>    several problems with changelog file (notably, the description was
>    way too terse)

FWIW, I'm closing these as wontfix/invalid.  These are all essential
packages, which per policy should not be depended on unless a versioned
dependency is needed - there's no reason to add multi-arch metadata to these
packages *unless* someone has a concrete example of a versioned dependency.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[email protected]                                     [email protected]

Attachment: signature.asc
Description: Digital signature

-- 
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

Reply via email to