FreeDesktop.Org at a Glance — Resolve & Fixed Bugs

Well as I tend to lean towards lots of stats, I am at it again. I’ve been pulling a snapshot of all FDO bugs daily (missed one day) for the past couple weeks, I hope to use these snapshots to get a core set of stats for QA purposes, here is my first “snapshot of a snapshot” 😉

One of the most telling statistics for LibreOffice is the number of bugs which are marked RESOLVED (encompassing a few sub categories) and more importantly RESOLVED – FIXED which is a designation which says “yes indeed there was a bug, but a patch has been committed to fix it”. Below is a table which shows data pertaining to these two things (RESOLVED & RESOLVED – FIXED) since 1/15/2013.

DATE Total # of Bugs Marked “RESOLVED” Resolved Bugs Per Day Sum of Resolved Bugs Per Day Total # of Bugs Marked “FIXED” Fixed Bugs Per Day Sum of Fixed Bugs Per Day
January 15th, 2013 7657 3226
January 16th, 2013 7676 19 19 3233 7 7
January 17th, 2013 7697 21 40 3242 9 16
January 18th, 2013 7706 9 49 3247 5 21
January 19th, 2013 7724 18 67 3249 2 23
January 20th, 2013 7732 8 75 3250 1 24
January 21st, 2013 75 24
January 22nd, 2013 7756 24 99 3258 8 32
January 23rd, 2013 7767 11 110 3261 3 35
January 24th, 2013 7788 21 131 3272 11 46
January 25th, 2013 7806 18 149 3278 6 52
January 26th, 2013 7815 9 158 3283 5 57
January 27th, 2013 7824 9 167 3285 2 59
January 28th, 2013 7842 18 185 3293 8 67

The information above is a bit messy but all in all here are some high points:

  • In the past 2 weeks or so we’ve marked 185 bugs as RESOLVED
  • Of those 185, 67 were marked as FIXED — again, this means that there was a confirmed bug that was fixed
  • Every day there was at least 1 bug fixed
  • The best day was January 24th, where 11 bugs were fixed in approximately a 24 hour period

While numbers alone can’t prove the tremendous amount of work done by developers on a given day — as example consider a day where only 1 bug is fixed but that single bug is hundreds of lines of code — the numbers are promising that we are daily achieving incredible progress towards our goal to make LibreOffice the best, most comprehensive, office suite available.

Just to add a nice looking chart to this data, here is a visual of bugs marked RESOLVED & bugs marked FIXED per day.

I’ll end it here with saying a big THANK YOU to all of the developers, QA, Marketing, UI, locale, documentation, etc.. etc… that make this project possible – without each of you, we would be left with nothing.

Thanks all, until next time

Best Regards,
Joel

Advertisements

About joelmadero

EE32 6D0F 81FF 6FAC 5AD8 10E4 0141 27C6 8FFB 1B14

5 responses to “FreeDesktop.Org at a Glance — Resolve & Fixed Bugs”

  1. Joren DC (@JorenDC) says :

    Thanks for these stats! I appreciate these number, and the underlying meaning of these numbers (the fixes that are made).

  2. Dennis says :

    Is there any possibility to create some automation of this task? (and maybe to do this on the official server/side, maybe ask at websites@global.libreoffice.org)

  3. joelmadero says :

    We are looking into this but it’s quite a task to automate, ultimately we’re hoping to use PyUno to do this. I’ll discuss it with website team going forward, first we need a clear idea of what stats we want to maintain. After I get about a month of data, the QA team and I are going to look at what we can do with it

  4. dennis says :

    any updates? New stats? XD

    • joelmadero says :

      I just did February stats last Friday so I’ll be writing up a blog this week hopefully. They are quite a bit more extensive so I may do several posts about them, dunno if demand for stats is that high 😉

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

%d bloggers like this: