Build failures as a proxy for archive quality

Thanks to it is easy to find out the build status of packages for multiple releases. In order to make sense of the number of build failures over a series of releases, you need to look at failure rates on a per architecture basis. So I made a chart:

Chart of FTBFS per architecture from Gutsy through Maverick

In broad terms it looks to me like we have made progress, but that the curve is flattening out. It’s nice to see though that we don’t have the same “release after LTS” bump that we had in Intrepid.  Notice the “*” next to Maverick. That’s because it’s not done yet. There is almost another full week to get Universe/Multiverse FTBFS fixes in, so let’s see if we can knock this down even further.


1 Response to “Build failures as a proxy for archive quality”

  1. 1 Roshan October 4, 2010 at 05:36

    Is it just me or are the axes labelled wrong?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: