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


Qa should run backtraces for the dev team. The dev team can focus on
implementing the fixes.  We should not ask end users to perform the traces.
If they are comfortable with doing it . Then this is great. As I was told
the wiki is for contributors and not end users.

Mas
On Sep 7, 2012 4:05 PM, "John Smith" <lbalbalba@gmail.com> wrote:

On Fri, Sep 7, 2012 at 9:59 PM, Joel Madero <jmadero.dev@gmail.com> wrote:
This isn't for end-users, it's for QA team......and it's our job to do as
much as possible to help the developers. I know when I'm doing the
development side I appreciate whatever previous info users and QA can
provide. It's maximizing the efficiency of our abilities....limited # of
developers means we should be using their time wisely, not running
backtraces that someone with 1/10th of their computer programming skills
could manage just fine.

Best Regards,
Joel

Well, like I said: I guess it all depends on who your target audience
is. Just keep in mind who that is, and what their expected skill set
is, and adjust your procedures to that. IMHO.

- John Smith.
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
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/


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.