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
On Fri, Sep 7, 2012 at 12:56 PM, John Smith <lbalbalba@gmail.com> wrote:
On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero <jmadero.dev@gmail.com> wrote:
I'll bring this up at our next conference call and see if there is a
possible solution.
Best Regards,
Joel
May I humbly note that I personally feel that developers should be
able to produce their own backtraces, given a solid reproducible
test-case in the bug report ? Perhaps effort would be better spend on:
1.)
teaching end-users how to provide a reproducible test case in a bug report
2.)
teaching devs on how to produce backtraces
instead of:
1.)
teaching end-users how to install symbol binaries and backtrace them
on their platform ?
Just my 2$
- John Smith.
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.