FW: STATE OF AOO: Overall Bugzilla Activity through July 2015
This message has received some discussion already on dev@ oo.a.o. I think it might be of particular interest for QA participants.
One clarification. The queries for open issues only counted issues that have no resolution of any kind. As far as Bugzilla queries go, issues in DUPLICATE, ..., WON'T FIX, and CLOSED state are viewed as resolved.
This analysis says nothing about the quality of those numbers, only that they are the numbers that we have at this high level of overview.
From: Dennis E. Hamilton [mailto:[hidden email]]
Sent: Wednesday, August 5, 2015 19:57
To: [hidden email] Subject: STATE OF AOO: Overall Bugzilla Activity through July 2015
In looking for visible indicators of project activity, I created an overview of Bugzilla activity from November 2012 through July 2015.
This is a high-level view of gross activity and does not provide fine details. There is still an interesting picture.
2012-11: #121299 First new issue in the Bugzilla of the AOO Top Level Project.
2015-07: #126439 Last new issue in the Bugzilla at the end of July, 2015.
By years, (2012 and 2015 partial)
2012 2013 2014 2015
929 2136 1739 441 BZ items/month
133 198 170 65 New issues/month
(averages are rounded to whole numbers)
As of 2015-08-05
* the oldest open issue is #497 created
* 24115 issues still open from before
* 2232 issues remain open of the 5139
new issues from November, 2012
through July, 2015
* 192 issues remain open of the 452
of those created in the first
7 months of 2015
The most noticeable aspects are the steady decline in monthly Bugzilla items (i.e., entries of all kinds) and in the number of those that are introduction of new issues.
The next observation is of the tremendous number of open issues that preceded the commencement of Apache OpenOffice following the incubation period begun in June 2011.
To see other patterns, it is necessary to examine finer details. I propose to do that only for 2015, so we have a better community understanding of what is happening with issues at this time.
I have no interpretation of these trends, and the burden inherited by Apache OpenOffice, other than noticing what they are.