Hi Sophie / Petr and all,
Thanks for the comments and ideas! I updated several wiki pages today to
outline what we got through the discussion. Please would you have a review and
feedback is appreicated :)
Details comes with:
1. Re-structure of QA page to put stuff into proper process.
http://wiki.documentfoundation.org/QA
I also updated the function test process part. From my understanding of
comments, Native Language QA is not considered as a single process since
what could be done is quite similar with Function QA, except that Native
Language QA may have different Test build and Test cases (though maybe part of
overlapping with) from function test.
L10n process is empty since it seems to be a different one.
2. Update the QA-team to outline a Test maintenance team:
http://wiki.documentfoundation.org/QA/QA_Team
3. Update a bit the BugReport Details page to put 'Severity' for concerning:
http://wiki.documentfoundation.org/BugReport_Details
The severity stuff is simply extracted from fdo documentation, we may want
to define them in more detail.
About the priority setting, I double checked the fdo documentation
https://bugs.freedesktop.org/page.cgi?id=fields.html#importance
which shows 'This field is utilized by the programmers/engineers to
prioritize their work to be done.'. In our case, not every bugs are
assigned when they are reported/triaged. So let me confirm we would like
this to be done in bug triage phase for not losing those high priority
bugs at the first time, though assigned developers can do further
adjustment via his/her own work states.
Best wishes,
Yifan
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.