Here's an update of the post about the size tracking of the Drupal 7 issue queue I made more than a month ago. January has been a pretty fruitful month for Drupal core development: we hit the point were the critical D7 issue queue halved in size. It reached its maximum around 15 October 2009 (code freeze) with 440 critical D7 issues and on Wednesday 27 January 2010, it dropped below 220.
Ok, maybe you consider this is a bit cheating, as 440 is the number of critical issues just before the code freeze, which has a bit of a positive bias. After the code freeze, the maximum size was 416, so that means that 208 is threshold to consider. But hey, at the time of this writing, the critical issue queue is at 211, so we're not far from that milestone too.
Below is the updated plot (click to enlarge).
Note that the critical issue queue shrinking is pretty bursty and irregular, which makes it very hard to make any prediction about when it will reach zero. Also, in case you wonder: the large drop around 8 january 2010 is sun's large critical issue cleanup (70+ issues).
Post new comment