Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 25/10/2011, v_2e@ukr.net <v_2e@ukr.net> wrote:
  Hello!
  Is it possible to see not only the total numbers of bugs on
categories, but also the "progress" in time? It is also interesting to
see the number of fixed (and not fixed) bugs on each new LO version.
Can I find such information?


"Progress" to what? Resolution of the error? This would be represented
by the ratio of fixed to unresolved bugs.

In terms of each LO version, have been thinking about a periodic
retrieval of the csv data for this summary table and then plotting the
results. If this was repeated on a monthly basis, you would see how
bugs resolution occurred during time, which would be interesting.

It is interesting to review this data. Since the first issue, the
total number of bugs has increased. There does not seem to be a method
of obtaining historic data which is a disappointment. The ratio of
bugs assignment to new bugs is less than 10 %; is this to be expected?

-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.