On 09/06/2012 06:55 PM, Michael Stahl wrote:
On 06/09/12 17:42, Michael Meeks wrote:
i don't have an opinion whether --enable-dbgutil should by default
enable symbols or not.
First of all, note that --enable-symbols is a misnomer. It is not
per-se about any kind of symbols (like not
Hi Petr, all,
On Thu, Sep 06, 2012 at 12:26:48PM +0200, Petr Mladek wrote:
Yi Fan Jiang píše v Čt 06. 09. 2012 v 03:47 -0600:
Yi Fan Jiang píše v Čt 06. 09. 2012 v 02:50 -0600:
4. In the page, make sure the version of the case is switched to
*0*
by:
- Around the top right
Yi Fan Jiang píše v Pá 07. 09. 2012 v 02:44 -0600:
Hi Petr, all,
On Thu, Sep 06, 2012 at 12:26:48PM +0200, Petr Mladek wrote:
Yi Fan Jiang píše v Čt 06. 09. 2012 v 03:47 -0600:
Yi Fan Jiang píše v Čt 06. 09. 2012 v 02:50 -0600:
4. In the page, make sure the version of the case is
Hi Petr,
On Fri, Sep 07, 2012 at 12:16:30PM +0200, Petr Mladek wrote:
BTW: Is it possible to easily copy test case from one version to the
other using the UI? Or is there some alternative of git cherry-pick
where you could apply changes to other branches?
Yes, the in-test-case version
There are 12 bugs from 2011 that haven't been triaged. I think they have
been kind of ignored because they require certain things (such as Mac or UX
input or advanced computer understanding :) ). Could someone(s) please get
these done, then at least we're up to 2012 :) If you see one or more that
Hi Nino,
That's the beauty of our project, everyone's opinion is respected :) I'll
try to avoid adding any work to website team and see what method works best
to get these triaged and organized best. As of now, google doc + fdo seems
to be doing the trick :) Ultimately might just make a macro to
Hi All,
Came across this bug FDO#45570 and I've already nominated as a most
annoying bug but I think that devs might appreciate me getting some kind of
a log or something together for the crash. What type of log should I create
and how do I go about doing this (basic steps, my knowledge of
On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero jmadero@gmail.com wrote:
Hi All,
Came across this bug FDO#45570 and I've already nominated as a most annoying
bug but I think that devs might appreciate me getting some kind of a log or
something together for the crash. What type of log should I
I don't see that helping much, as the developer who takes this one can
quickly do this themselves. A working doc only takes 2 seconds to make.
Best Regards,
Joel
On Fri, Sep 7, 2012 at 9:35 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 6:11 PM, Joel Madero
On Fri, Sep 7, 2012 at 6:38 PM, Joel Madero jmadero@gmail.com wrote:
I don't see that helping much, as the developer who takes this one can
quickly do this themselves. A working doc only takes 2 seconds to make.
Best Regards,
Joel
Another random thought then: Is there a way to reproduce
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and
functioning, I had 5 open FDO tabs in FF and picked the wrong one.
https://bugs.freedesktop.org/show_bug.cgi?id=48569
My apologies
Joel
On Fri, Sep 7, 2012 at 9:57 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep
On Fri, Sep 7, 2012 at 6:59 PM, Joel Madero jmadero@gmail.com wrote:
Wrong Bug, dammit, my bad. Here is the proper one, attachment is there and
functioning, I had 5 open FDO tabs in FF and picked the wrong one.
https://bugs.freedesktop.org/show_bug.cgi?id=48569
My apologies
Joel
Maybe
Hi John,
On Fri, 2012-09-07 at 19:10 +0200, John Smith wrote:
Maybe im just dumb, but: Once you have provided a reliable and
reproducible test case (in this case, download the odt file attached
to the report and save it as docx in libreoffice), is there still a
need to provide further info at
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved quickly. Ways to do that are:
* getting a stack-trace with full debugging
On Fri, Sep 7, 2012 at 10:44 AM, John Smith lbalba...@gmail.com wrote:
On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks michael.me...@suse.com
wrote:
Hi John,
You can always make it easier for a developer to solve - and the
easier
it is, the more likely it is to get solved
The best solution would be to have a debug symbol server, then there
would be easily accessible debug symbols even for the release builds.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings:
On Fri, Sep 7, 2012 at 9:42 PM, Joel Madero jmadero@gmail.com wrote:
Sounds good, but I agree with John that better instructions are needed. I'm
working on a new triage page and hopefully in there we can get someone to
contribute incredibly precise, easy for noobs, instructions for every
On Fri, Sep 7, 2012 at 9:49 PM, Joel Madero jmadero@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
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 abilitieslimited # of
developers
On Fri, Sep 7, 2012 at 9:59 PM, Joel Madero jmadero@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.
20 matches
Mail list logo
