Category Archives: Release-Team

The release team receives an extreme amount of unblock requests right now.  For the past 22 days[1], we have been receiving no less than 408 unblock/ageing requests.  That is an average of ~18.5/day.  In the same period, the release team … Continue reading →

The release team are doing a sprint right now up the mini-DebConf in Cambridge, kindly hosted by ARM. We have a fairly large agenda of around 10 items, ranging from “simple” things like determine the name for the next release … Continue reading →

As mentioned by Raphaël Hertzog, I have been spending some time on improving Britney2.  Just the other day I submitted a second branch for review that I expect to merge early next week.  I also got another set patches coming … Continue reading →

Today, we held an one-hour IRC-meeting to debate the status of the current architectures in sid.  During that one hour, we brought up all 13 architectures.  We made a decision on 9 of the architectures.  The remaining 4 will be … Continue reading →

I am very pleased to say that RC bug counter for Jessie finally dropped below 500 RC bugs.  For comparison, we broke the 700 RC bug curve in the start of November, so that is about 200 RC bugs in … Continue reading →

It looks like we have dropped (or will drop) below 700 RC bugs affecting Jessie today[1].  🙂 On a related note, I got my eye on libfso-glib + fso-gsmd, samba + -samba4, mono and haskell.  By my count, each of … Continue reading →

Early this month, the first batch of packages were automatically removed from testing due to RC bugs.  Personally, I find that the results stand out pretty well on the RC bug graph[1].  There has been a very rapid decline in … Continue reading →

In my previous post, I explained about the “age” excuse in Britney.  In this post, I will cover the slightly more tricky “out of date” excuse.  A simple example of excuse is: out of date on mipsel: blinken (from 4:4.8.4-1) … Continue reading →

Every package maintainer has probably looked at the “Testing migration” section of their package’s PTS page and wondered: “Okay? What the hell does that mean?”.  Or perhaps “Is that something I should do something about?”.  Lets have a look at … Continue reading →

During the Wheezy freeze, the Debian release team deployed 3254 hints[1].  This number may include some duplicates (i.e. where two members of the team hinted the same package), it certainly does not include a lot of rejected requests . The … Continue reading →