On Mon, 01 Apr 2013 00:48:08 +0300 Uoti Urpala <uoti.urpala@pp1.inet.fi> wrote: > Philipp Kern wrote: > > On Sun, Mar 31, 2013 at 12:33:46PM -0500, Dirk Eddelbuettel wrote: > > > I cannot influence the R release cycle which happens within our freeze. As > > > have a few previous R releases, and none of those created any trouble. > > > > Thanks for trading the R release cycle with Debian's and for delaying the > > release. The harm has already been done, so somebody should probably go > > and create a transition tracker for it? > > IMO it's important to remember that it's fundamentally the release team > that is at fault for problems here, not the R maintainer. The length of the freeze is not the fault of the release team. The length of the freeze is down to all of the contributors to Debian not fixing enough RC bugs - I count myself in that, I've managed to get massively less done for this release than for previous ones. There are reasons, it doesn't change the reality that the freeze is still ongoing. The release team have been looking for help to triage unblock requests and some help has been given, but even if unblocks were all handled, there remain too many RC bugs and that is and always has been the core problem. The release team are not responsible for fixing RC bugs - that's down to the rest of us. Release-critical bugs delay releases, not the release team. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgp0QUVABcoet.pgp
Description: PGP signature