Very interesting, thank you. Perhaps the reduced activity is an indication for the saturation state of the project (i.e. all the possible bugs and features already exist in Bugzilla)? Is it possible to compare this information with other office suites?
On Fri, Jan 15, 2016 at 9:22 PM, Dennis E. Hamilton <orc...@apache.org> wrote: > [BCC to Project Management Committee and users@ oo.a.o] > > SUMMARY > > The top-level analysis of Bugzilla issue handling has been completed for > all issues opened on the project through December 31, 2015. > > The complete tabulation is in the PDF document at <http://s.apache.org/YFT > >. > > It remains the case that since the establishment of Apache OpenOffice as > an ASF Top Level Project in November, 2012, the accrual of unresolved > issues exceeds 40%. That is, for every 100 new issues, on the average more > than 40 of them will be unresolved indefinitely. > > In contrast, although there is a very large number of unresolved issues > that remain in the Bugzilla from its history as part of OpenOffice.org, > that previous technical debt was, proportionally, under 20%. > > Some highlights: > > * Even though the monthly rate of new issues and comments on issues has > been decreasing significantly since mid-2014, the rate of technical debt as > the proportion of unresolved issues has not improved. > > * Although a reduction to 35% unresolved-issue is seen in the last 5 > months of 2015, this may be distorted by issues created and then resolved > in the staging of AOO 4.1.2 release candidates and QA on the candidates. > Results for the first-quarter of 2016 are needed to determine if this is a > new trend or a hiccup. > > DETAIL AND QUALITY MATTERS > > This is a rough analysis, although the consistent trend is difficult to > explain away. > > Refinement requires a closer look at the nature of issues and > understanding of exactly what resolution means, not just what being left > unresolved means. > > There is also a suspected disconnect with regard to what is considered an > issue and how the ways of closing an issue are actually applied. > > * Closing of a new issue as a duplicate qualifies as a resolution. The > incidence of long-standing issues that continue to receive duplicate > reports is useful to understand in this case, and that requires more detail. > > * Some issues are closed as Resolved Fixed when the fact of the matter is > that there was insufficient detail to understand and confirm the issue and > the reporting party failed to provide additional information (if it was > even requested). > > * Some comments on issues tailgate possibly-different problems onto known > ones, although the resemblance may be superficial and the issues need to be > split. > > * Enhancement/feature requests are not distinguished. > > * Resolved issues are sometimes closed without obtaining confirmation > that incorporation of the identified resolution in distributed code > actually addresses the originally-reported difficulty. > > * Some issue reports are closed as not issues because they are declared > user problems and kicked to the Community Forum. > > These may all have small effects. We will know only by looking more > closely into Bugzilla details. > > The last case deserves more careful attention. > > The next-in-line users of Apache OpenOffice distributions consist of > around 50 million users who are mainly individuals and 87% of whom are > using Microsoft Windows. Such casual users, whatever their limited > experience in trouble-shooting and describing problems, are the main users > of this software. The usability issues they encounter are important to the > project; even though they may not involve bugs in the code, they point to > defects in the product. Capturing those experiences and recognizing them > as real issues for the user community is important. That feedback is > important for determining and making available workarounds and advice. It > can also inform changes to the software that might ameliorate those > difficulties for non-experts. Here's a simple example: having an > easy-to-use option for resetting the user profile. > > FUTURE STEPS > > Along with extending the current analysis into the first quarter of 2016, > exploration of the nature of unresolved and resolved issues will be > introduced. > > > - Dennis > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
