Hi, another week and Sunday gone, but this time i tried to look a bit closely to the numbers...
340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) 325 regressions <-- release announcement + 4weeks 326 regressions <-- release announcement + 5weeks(rc3) 325 regressions <-- release announcement + 6weeks(rc4)
3rd week in a row and unfortunately these numbers don't change significantly to zero. Based on these following numbers we can't even say, that we close at the same rate as new are opened. Closer look to "fixing" capacity or in other words what is behind -1 fixed regression for this week:
+24 Newly marked, opened (new/unconfirmed) -16 Closed, resolved fixed -09 Not a regression (invalid, duplicate) ==== -1
More IN than OUT could show that stable release is far a way.
Another relese barometr could be Milestones 1.2:
59 bugs <-- release announcement + 5weeks(rc3) 46 bugs <-- release announcement + 6weeks(rc4)
Decoding shows much better numbers than in case of regressions: +02 Newly marked, opened (new/unconfirmed) -11 Closed, resolved fixed -04 Not a Milestone-1.2 ==== -13
W.