On Tue, Mar 28, 2017 at 05:16:21PM -0700, Sean Whitton wrote: > Hello Branden, > > On Tue, Mar 28, 2017 at 05:28:25PM -0400, G. Branden Robinson wrote: > > > You are very unlikely to get release team approval for this upload as it > > > stands. Given what you wrote in #511645, is your intention for xtrs to > > > drop out of stretch, to be reintroduced in buster? > > > > I've been making conservative (pessimistic) estimates about how fast I'd > > be getting things done since I'm freshly back to the project after a > > long absence. There were and are best practices I need(ed) to get > > caught up on. I also couldn't be absolutely sure I'd get a sponsor > > before the removal-from-testing date (scheduled for 11 April); I don't > > know when I'll be able to get my new GPG key into the Debian keyring so > > that I can upload under my own power[1], and so forth. Finally, I don't > > want to cause the release team any trouble. > > > > So my goals were, in this order: > > 1) Get the package suitable for unstable (which it wasn't); then > > 2) Get the package suitable for testing. > > Generally speaking, something shouldn't go into unstable unless it would > also be suitable for testing (once deps and r-deps are also ready to > migrate). It'll be suitable for testing for Buster, that's for sure. My bad luck to return during a release freeze. I'm interested in the least-effort solution (for other people) that doesn't involve shipping a badly broken package in Stretch. -- Regards, Branden
Attachment:
signature.asc
Description: PGP signature