You can often export the bug database out into excel for analysis. You may need to play with the results to focus on problem reporting.
Why? Often open source projects end up with "wish list" bugs that do not fall within anyone's funding or mandate. Personally I would love to see the difference not between open source and proprietary software - as I think that sells us short (we are more amazing than that!). The true test would be the track record for paying customers - getting a bug fixed with an open source product vs a proprietary product. Since a common open source model is to pay for support; it would be great to show the amazing service provided. Now that *would* be an impressive difference. Jody On Thu, Nov 11, 2010 at 7:43 PM, Sjur Kolberg <sjur.a.kolb...@sintef.no> wrote: > Hello, > > Is there any mechanism in the bug tracking systems being used, that can > export the distribution (histogram or mean) of time taken from a bug report > is filed to it is declared successfully closed? > > I guess I could figure that out manually by reading through all tickets; > that is probably not going to happen... > > > > I am trying to convince people that open source GIS is a better solution > than buying proprietary software. Such discussions follow a well-known path > (is it mature/stable? How about support? All our clients use XXXX..., Nice > for programmers, but...) etc. Conclusions precede arguments, and some hard > numbers could be of great help in all the religion. > > > > Best regards, > > Sjur K :-) > > > > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss > > _______________________________________________ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
