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

Hi Stuart,
I agree that when we report bug we should do what we can to supply as much information as possible. The problem here - from my point of view - is that a lot of issues was marked as NEEDINFO by mistake. I have at least one (and its my impression that there are more) that doesn't need any info. All it needs is a little attention from the QA/devs.

I have posted some issues over time but I don't think I will bother in the future. My time seems to be not appreciated?

The bug has never been commented by humans and all later activity was automated (except the once from my hand).

If QA and dev groups think this approach is the right way to go then I am afraid that we will have huge difficulties finding new non-programmers participate in the QA-process.

Half the problem is communication. If the process has been more clear and accurate it wouldn't have been a problem. Why not explain the process and the reason for closing these issues? Why not explain what it means that the issue has been closed? Why not explain what the owner could do to re-invoke the issue? Why not find another status that "RESOLVED INVALID". These issues are not resolved nor invalid.

i try to encourage people to submit issues if they have problems. I also try teach them to give enough information. But some are not very good at English and others are not very technical minded. These "amateurs" got scarred and will stay away in the future. That is not what we need at current. We need to embrace and encourage - not scare away.


On 15-08-2012 19:20, V Stuart Foote wrote:
Yes the apology was issued over on the Dev and QA lists--inserted below.
But we folks on the QA and User side do have a responsibility to follow our
bugs when posted, and to participate when calls for NEEDINFO are issued. And
also, that when bugs are closed we reopen them with careful attention to the
information needed to fully describe the bug and the quality of detail the
Devs will needs to resolve.

Otherwise, let's move on folks!


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.