On Fri, Apr 26, 2013 at 12:36 PM, Bjoern Michaelsen <[email protected]> wrote: > > So, as a developer, I would think comments (and the platform field) would be > sufficient for these rare cornercases. > > For fixed and reappearing, I think its > not really an issue: > - if the bug is really fixed, it should have a dev having insight in the some > issue already (and reading a few comments is not so much work compared to > the > total effort in these cornercases) > - if the bug was not fixed but just "disappeared" -- that is, stopped being > there without a dev claiming to intentionally having fixed it, it is likely > a > Heisenburg anyway and the version info to be used carefully (or even > ignored) > anyway.
If the developers think that the current system provides enough information for them to fix the bugs, then perhaps we don't need to make any updates to the system for the devs, which is good to know. My thought was that a cleaner, more visual display of the information could be helpful for people doing QA (both on the team or just regular users) to understand the helpfulness of narrowing-down the precise point at which a bug was introduced into the code. The FDO interface can be very cryptic! I don't know if an easier-to-read interface would increase our ability to attract users to join us and help us retain people as members of the QA Team, but it is one of the things I thought about when making a mock-up. We definitely need to grow our ranks to be able to address the influx of bug reports. Cheers, --R _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
