February Bug Stats

Well it’s a few weeks late (apologies) but, isn’t there a saying about “better late than never” :-D

Below is a list of daily (almost at least) change of total number of bugs reported against LibreOffice on FreeDesktop.Org (FDO). During the month 1,043 bugs were reported, averaging out at just over 37 bugs per day. While this could be looked on as a negative, I tend to be excited that we have enough user base and involvement that we are getting this kind of activity on FDO. On our most active days we were hitting over 80 bugs reported in a single day which is incredible (please keep in mind that some portion of these are duplicates). This being said, the other important note is that our QA team is way under staffed to handle this number of bugs, assuming there are 10 of us triaging somewhat frequently we’d need to triage over 100 bugs a month along with our other duties — including “real” (paid) work, school, and of course our personal lives. This is just further proof that we need to reach out to the community and get more people involved with QA work – ideally IMO we would be at no more than 30 bugs per month per person on average which means we need to triple our current number of regular triagers (again assuming we currently have 10 “regularly involved”)

Total Bug Count on FDO

Date

Bug Count

Change

01/31/13

16011

02/01/13

16032

+ 21

02/02/13

16055

+ 23

02/03/13

16094

+ 39

02/05/13

16146

+ 52

02/06/13

16174

+ 28

02/07/13

16205

+ 31

02/08/13

16266

+ 61

02/10/13

16354

+ 88

02/11/13

16390

+ 36

02/12/13

16439

+ 49

02/13/13

16491

+ 52

02/14/13

16524

+ 33

02/16/13

16604

+ 80

02/17/13

16630

+ 26

02/18/13

16678

+ 48

02/19/13

16711

+ 33

02/20/13

16742

+ 31

02/21/13

16790

+ 48

02/22/13

16830

+ 40

02/23/13

16878

+ 48

02/24/13

16920

+ 42

02/25/13

16938

+ 18

02/26/13

16974

+ 36

02/27/13

17007

+ 33

02/28/13

17054

+ 47

Total

+ 1043

Then we have the number of bugs that were in status NEW & RESOLVED.

A majority of the NEW bugs came from either UNCONFIRMED to NEW or from NEEDINFO to NEW. Both of these are telling as they mean the bug was confirmed with the given information and therefore can move forward in the process of trying to get the issue fixed. The majority of this work can be credited to our awesome QA team who do a tremendous job ensuring that the information that is needed is on the bug report as well as manually testing each bug one at a time.

With the RESOLVED bugs, the majority of the credit goes to our amazing Development team who move bugs from NEW & REOPENED status to RESOLVED. This being said some of these bugs are closed as RESOLVED for other reasons including WORKSFORME (QA mostly) and DUPLICATE (QA & Dev team).

New & Resolved Counts
Date New New – Change Resolved Resolved – Change
01/31/13 4261 7884  
02/01/13 4277 + 16 7904 + 20
02/02/13 4294 + 17 7920 + 16
02/03/13 4302 + 8 7928 + 8
02/05/13 4297 - 5 7956 + 28
02/06/13 4294 - 3 7975 + 19
02/07/13 4306 + 12 7999 + 24
02/08/13 4303 - 3 8040 + 41
02/10/13 4349 + 46 8068 + 28
02/11/13 4364 + 15 8091 + 23
02/12/13 4371 + 7 8114 + 23
02/13/13 4385 + 14 8135 + 21
02/14/13 4391 + 6 8151 + 16
02/16/13 4422 + 31 8194 + 43
02/17/13 4429 + 7 8211 + 17
02/18/13 4413 - 16 8242 + 31
02/19/13 4432 + 19 8259 + 17
02/20/13 4444 + 12 8296 + 37
02/21/13 4464 + 20 8315 + 19
02/22/13 4475 + 11 8332 + 17
02/23/13 4498 + 23 8354 + 22
02/24/13 4523 + 25 8376 + 22
02/25/13 4524 + 1 8386 + 10
02/26/13 4534 + 10 8427 + 41
02/27/13 4541 + 7 8451 + 24
02/28/13 4538 - 3 8472 + 21
Total   + 277   + 588

During the course of the month there was an increase of 277 bugs in NEW status on a day over day basis while there was an increase of nearly 600 on a day over day basis to RESOLVED.

NOTE: Just to be accurate, this does not accurately portray exactly how many bugs were put into NEW or RESOLVED in a given day because a bug could have gone from NEW to RESOLVED in a single day, counting for 1 on “RESOLVED” column but not 1 on “NEW” status – remember this is only a snapshot of FDO.

As stated above, DUPLICATES are a part of the “RESOLVED” category and offer a lot of insite for individual bugs – most notably it’s a way to gauge how many people are affected by a single bug. In the long run we hope that more bug reporters are able to leave comments on existing bugs instead, but for the time being, a DUPLICATE bug reflects well on QA/Devs (for identifying the dupe), our users (for reporting the bug) and on our product (for offering insite on importance of a bug).

Duplicates
Date All Versions – Total Count All Versions – Change Version 4.0+ – Total Count Version 4.0+ – Change
01/31/13 1916 85
02/01/13 1923 + 7 87 + 2
02/02/13 1925 + 2 88 + 1
02/03/13 1925 0 88 0
02/05/13 1931 + 6 90 + 2
02/06/13 1935 + 4 91 + 1
02/07/13 1941 + 6 94 + 3
02/08/13 1951 + 10 100 + 6
02/10/13 1963 + 12 107 + 7
02/11/13 1967 + 4 107 0
02/12/13 1974 + 7 111 + 4
02/13/13 1982 + 8 116 + 5
02/14/13 1987 + 5 117 + 1
02/16/13 2003 + 16 124 + 7
02/17/13 2010 + 7 129 + 5
02/18/13 2014 + 4 129 0
02/19/13 2018 + 4 132 + 3
02/20/13 2037 + 19 148 + 16
02/21/13 2044 + 7 152 + 4
02/22/13 2050 + 6 158 + 6
02/23/13 2056 + 6 163 + 5
02/24/13 2065 + 9 172 + 9
02/25/13 2066 + 1 173 + 1
02/26/13 2072 + 6 178 + 5
02/27/13 2074 + 2 178 0
02/28/13 2078 + 4 182 + 4
Total   + 162   + 97

The release of Version 4.0 was an important milestone, because of this I’ve divided the columns between “all versions” and just 4.0+ bugs. As you can see over 160 open bug reports were closed as DUPLICATE during the month, more than ½ of which were against Version 4.0.

Now on to some regressions. With the release of 4.0.0.x release we had to account for how many regressions were reported against releases prior to 4 and those reported against 4. The below table has this break down as well as showing how many regressions were in status NEW – this means that the bug was a) confirmed and b) not fixed yet.

Regression Stats
Date All Versions – Total Count All Versions –Status NEW Version 4.0+ – Total Count Version 4.0+ Status NEW
01/31/13 1199 174 244 46
02/01/13 1203 176 250 48
02/02/13 1204 178 252 50
02/03/13 1211 182 257 54
02/05/13 1219 183 260 54
02/06/13 1222 182 259 50
02/07/13 1224 184 263 51
02/08/13 1230 187 267 52
02/10/13 1250 193 286 59
02/11/13 1254 194 289 60
02/12/13 1259 192 292 58
02/13/13 1262 193 293 59
02/14/13 1267 193 297 59
02/16/13 1282 194 308 58
02/17/13 1289 197 314 60
02/18/13 1292 197 317 60
02/19/13 1301 200 323 63
02/20/13 1307 201 329 65
02/21/13 1311 199 331 65
02/22/13 1314 199 334 66
02/23/13 1319 200 339 68
02/24/13 1324 200 342 68
02/25/13 1327 200 344 68
02/26/13 1333 199 348 69
02/27/13 1337 200 352 71
02/28/13 1340 195 355 68

While the number of regressions grew quite rapidly ruing the period (climbing by 141 bugs in the month) the number of NEW bugs remained relatively stable (increasing by only 22), most of this is credit to our development team who made sure to tackle regressions efficiently & effectively.

FIXED bugs are obviously one of our “shining lights” of the project, they indicate a complete and total workflow for bugs, from reporting, to triaging, to fixing – this of course includes dev team, users and QA team and often times other teams get involved in the process to help ensure all information is there, offer opinions/alternative solutions, etc….

Marked as FIXED
Date All Versions – Total Count (FIXED) All Versions –Status FIXED Version 4.0+ – Total Count (FIXED) Version 4.0+ – FIXED % Version 4 Fixed/Total Fixed (CHANGE)
01/31/13 3313   262    
02/01/13 3319 6 266 4 40.00%
02/02/13 3328 9 270 4 30.77%
02/03/13 3334 6 271 1 14.29%
02/05/13 3352 18 276 5 21.74%
02/06/13 3360 8 280 4 33.33%
02/07/13 3367 7 282 2 22.22%
02/08/13 3388 21 291 9 30.00%
02/10/13 3395 7 293 2 22.22%
02/11/13 3404 9 297 4 30.77%
02/12/13 3417 13 305 8 38.10%
02/13/13 3421 4 304 -1 -33.33%
02/14/13 3427 6 308 4 40.00%
02/16/13 3444 17 315 7 29.17%
02/17/13 3446 2 316 1 33.33%
02/18/13 3451 5 320 4 44.44%
02/19/13 3454 3 323 3 50.00%
02/20/13 3462 8 325 2 20.00%
02/21/13 3469 7 328 3 30.00%
02/22/13 3474 5 331 3 37.50%
02/23/13 3479 5 334 3 37.50%
02/24/13 3485 6 334 0 0.00%
02/25/13 3490 5 335 1 16.67%
02/26/13 3503 13 341 6 31.58%
02/27/13 3514 11 347 6 35.29%
02/28/13 3525 11 355 8 42.11%

Again in order to highlight the importance of 4.0 we’ve split the columns to “all versions” and just version 4. As you can see the number of fixed bugs per day were impressive, more than 10 bugs were fixed on a single day. Also of importance is the fact that ~45% of fixes were against 4.0, showing that we are both dedicated to our new version as well as maintaining our older releases.

Last fun stat for this blog, # of comments. I thought it’d be interesting to look at number of comments as an indicator of how active FDO is.

Total # Of Comments
Date All Versions – Total Count All Versions –Status Version 4.0+ – Total Count Version 4.0+ % Version 4 Fixed/Total Fixed (CHANGE)
01/31/13 102,158   5,781    
02/01/13 102,342 184 5,851 70 0
02/02/13 102,511 169 5,924 73 0
02/03/13 102,658 147 5,985 61 0
02/05/13 102,987 329 6,131 146 0
02/06/13 103,164 177 6,182 51 0
02/07/13 103,376 212 6,269 87 0
02/08/13 103,721 345 6,462 193 0
02/10/13 104,256 535 6,787 325 0
02/11/13 104,450 194 6,881 94 0
02/12/13 104,750 300 7,033 152 0
02/13/13 105,033 283 7,179 146 0
02/14/13 105,256 223 7,291 112 0
02/16/13 105,704 448 7,506 215 0
02/17/13 105,915 211 7,633 127 0
02/18/13 106,154 239 7,749 116 0
02/19/13 106,375 221 7,884 135 0
02/20/13 106,658 283 8,042 158 0
02/21/13 106,957 299 8,222 180 0
02/22/13 107,183 226 8,368 146 0
02/23/13 107,412 229 8,518 150 0
02/24/13 107,681 269 8,670 152 0
02/25/13 107,799 118 8,741 71 0
02/26/13 108,145 346 8,927 186 0
02/27/13 108,372 227 9,058 131 0
02/28/13 108,598 226 9,202 144 0

As you can clearly see, we’re quite popular :) 6,440 comments were posted during the month (yes that is OVER 6,000 comments. Incredible. Of these 3,421 were reported against version 4 (just over 50%).

NOTE: Comments include the auto comments for fixed bugs, impossible (or nearly impossible) for me to figure out what % of the total number of comments came from bots but, 6,440 comments is none the less very impressive IMO.

With that I’ll end this months (or last months, or the month before that) stats blog. I know that I didn’t do the same stats as the previous month, trying to keep it “fun and new”.

Feel free to ask for specific stats or suggest anything that comes to mind.

Best to all :-D

Joel Madero

P.S. Apologies for now pretty charts, wordpress is being slightly difficult today, might add them later if requested :)

About these ads

About joelmadero

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

3 responses to “February Bug Stats”

  1. Sergeant says :

    Let’s assume I want to help with squashing bugs (and I do). And lets assume I have programming experience (and I have). And lets assume when I say programming experience, I mean I’ve dabbled in Pascal, BASIC and a little VBA. Lets also assume I haven’t done this for at least 10 years and am very behind modern language structures and capabilities.

    What books (references please) would I need to obtain to (re)teach myself whatever LibreOffice is programmed in. I’m assuming it’s C or C++ off the top of my head. I’m trying to understand “modern” object-oriented based languages and IDE’s but as I’ve said my primary programming knowledge dates back 20 years in structured basics (think commodore 128 basic, etc).

    I’ve got some books on OOP but find some concepts difficult to understand due to the change in terminology and their expanded capabilities.

    I would love to help but am finding it difficult to find sufficient resources at a sufficiently basic level to build my understanding of modern programming concepts such as classes, methods, objects, etc.

    Yes, I know how to program. But being out of it for so long and being so behind the new technology, I’m confused.

    • joelmadero says :

      I think that this really comes down to how you learn as an individual. I’m more of a “learn by doing” type of person so the few programming books that I have are sitting around collecting dust. Here is how I would approach your situation:

      Join Developer & QA Mailing Lists – http://www.libreoffice.org/get-help/mailing-lists/, be aware that you will get some traffic but not overwhelming, easy enough to filter them into a folder

      Join Developer & QA IRC room – here you will find a group of us (quite a large group) that are always available to help. Note that we come from all areas of the globe so you’ll have to get used to how some people speak (some people are quite blunt, that’s just how it is) but almost everyone will go above and beyond to help you out.

      By doing these two things you immediately become part of the community, furthermore, you get to see how we interact and how welcoming the group is.

      From here I would join QA work first – I am a member of the core QA team and can say from experience that the best way for a new user to get involved is to dive into QA, help us triage bugs, learn how to build libreoffice, etc…quite a few members of QA started in QA and now do both development and QA work (including myself to a very limited degree….my programming skills are quite limited, furthermore, QA takes up a few hours a day as is ;) ) QA doesn’t require programming skills at all, if you bring even limited programming skills to the table, you’re very much in a great position to help. Furthermore, QA is understaffed and could use the help ;)

      after you join QA and start triaging/building libreoffice, you can start exploring the code, and this is where I was able to learn a ton, just looking at the structure and picking easy hacks along the way.

      https://wiki.documentfoundation.org/Development/Easy_Hacks_by_Difficulty

      Feel free to contact me directly or to ping me in IRC, I’ll do my best to help you get involved. Thanks for showing interest, we’d love to have you on our team(s)

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

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: