On Tue, 6 Nov 2012 14:17:05 +0100 Thibaut VARENE <varenet@debian.org> wrote: > On Tue, Nov 6, 2012 at 1:04 PM, Neil Williams <codehelp@debian.org> wrote: > > On Tue, 6 Nov 2012 10:59:42 +0100 > > Thibaut VARENE <varenet@debian.org> wrote: > > If you want it in Debian now, push it into experimental. If you want it > > Jessie (the next testing), then wait for the d-d-a announcement. If you > > wanted it in Wheezy it's too late. If you just wanted it in unstable > > then it's clear that this is not desirable and your only option is > > experimental. > > Noted. The package was in experimental for several weeks and got zero > attention. Hopefully because people are working on the release so that uploads to unstable can be opened again. The quicker we release Wheezy, the quicker this and other packages get into unstable. It's much better to work on RC bugs than to worry about a migration which can't really start until after the freeze. > My general understanding is that nobody looks at > experimental anyway. Those who do work other than on RC bugs during a release freeze will use experimental. It's where all the updates happen which are not intended for inclusion into the currently frozen testing. > Another part of the issue was upstream's will to > have it in Ubuntu as soon as possible. Ubuntu autosync doesn't fetch > from experimental. Co-ordinate that with Ubuntu - the version of a package in Ubuntu does not affect how Debian makes a stable release. Whilst the wishes of upstream can be met outside of a freeze, there must always be extra barriers to package updates during a freeze or it wouldn't be a freeze. The will of upstream typically becomes a wishlist bug in Debian and wishes can't be met during a freeze, generally. Having a freeze simply means that some package changes *must* be delayed until after the freeze. Experimental works for some, if it doesn't work for you then you cannot update the package in Debian until the release, so maybe help get the release out. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpD0TLl64Q9Y.pgp
Description: PGP signature