[Bug Triage]
+ Related wiki: http://wiki.documentfoundation.org/BugTriage
1. The current bug triage process looks working very well. One thing in
lack of fields like:
- 'NEEDINFO'
- 'UNCONFIRMED'
- etc.
Is somebody working on them? And any other field of current bugzilla is better
off being improved?
2. Multiple language bug reports
I ever saw bugs opened in French, German and Chinese. Some of them were
kept alive when somebody translated while some of them were closed as
invalid since people ignored them.
So do we need an explicit rules for those? After all Libreoffice is being
used by people in the world. We may overlook those real bugs reported by
closing them immediately.
A possible process for such a situation is, instead of setting those bugs
as invalid immediately, to set a timeout threadhold (10 days for
example)to wait a non-English bug translation. After the timeout, we close
the bug as Invalid.
Another solution (great one) might be l10n people add their names to the
http://www.freedesktop.org/wiki/Software/LibreOffice/FindTheExpert
wiki page. Then we could put the names into CC and ask for a translation?
How do you see that?
--
Yifan Jiang
Libreoffice
Contact: yifan - irc.freenode.net/libreoffice
=============================================
http://www.libreoffice.org/
http://www.documentfoundation.org/
Context
- [Libreoffice] Libreoffice QA Review and Feedback Gathering - Bug Triage · Yifan Jiang
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.