Petr Mladek schrieb:
IMHO, the most important is to give
user chance to answer before the first warning (30 days or so).
Hi Petr,
I don't think so. My experience is that the reporter normally will
answer within 3 days (mostly: latest next day) or never. We should not
base our decisions on 1
Hello everyone,
Am 28.01.2013 14:13, schrieb Petr Mladek:
On Mon, 2013-01-28 at 10:05 +0100, Rainer Bielefeld wrote:
Petr Mladek schrieb:
[...]
BTW, I dislike the "noise" the discussed "3 strikes" solution will
cause. I'm thinking about a different solution:
I think most of you know, that I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Resending with more info.
Em 28-01-2013 17:09, Kohei Yoshida escreveu:
> On 01/28/2013 10:52 AM, Kohei Yoshida wrote:
>> I have hard time reproducing this bug
>>
>> https://bugs.freedesktop.org/show_bug.cgi?id=59850
>>
>> Can someone do a bit more tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em 28-01-2013 17:09, Kohei Yoshida escreveu:
> On 01/28/2013 10:52 AM, Kohei Yoshida wrote:
>> I have hard time reproducing this bug
>>
>> https://bugs.freedesktop.org/show_bug.cgi?id=59850
>>
>> Can someone do a bit more triaging to narrow it down a
On 01/28/2013 10:52 AM, Kohei Yoshida wrote:
I have hard time reproducing this bug
https://bugs.freedesktop.org/show_bug.cgi?id=59850
Can someone do a bit more triaging to narrow it down a bit?
And many thanks for those who've chipped in!
All the best,
Kohei
--
Kohei Yoshida, LibreOffice h
Also, in order to avoid 100's even at the beginning, why don't we split the
100's up and do them over several weeks? I can take care of this if it's
the decision. I can filter by date and do maybe 2 week increments - I
believe the oldest NEEDINFO bug is from nearly a year ago with no activity.
Thou
I have hard time reproducing this bug
https://bugs.freedesktop.org/show_bug.cgi?id=59850
Can someone do a bit more triaging to narrow it down a bit?
Thanks,
Kohei
--
Kohei Yoshida, LibreOffice hacker, Calc
___
List Name: Libreoffice-qa mailing list
On 01/28/2013 04:57 AM, Petr Mladek wrote:
On Sat, 2013-01-26 at 14:27 -0800, Joel Madero wrote:
+Assigning Bugs
-AGREED: At this time QA team “pushing” bugs to developers
isn't working, we will now only do “pull” philosophy (developers
choose their own bugs and assign themselves
Hi Joel, all
jmadero wrote
> d) a "3 strikes" type system - send one reminder, a month later send a
> second with a warning the bug will be closed, then close the bug
+1
but this sounds like a lot of human work...
How can you make sure that a reply is noticed (e.g. after first reminder) so
tha
Sorry for the double post.
Le 2013-01-28 06:58, Florian Effenberger a écrit :
Hi,
Rainer Bielefeld wrote on 2013-01-26 17:13:
Do we really need a copy of the readme on the site?
[..]
I also doubt that such copy is necessary. If we need it because of legl
reasons, we need a TOC with links
Le 2013-01-28 06:58, Florian Effenberger a écrit :
Hi,
Rainer Bielefeld wrote on 2013-01-26 17:13:
Do we really need a copy of the readme on the site?
[..]
I also doubt that such copy is necessary. If we need it because of legl
reasons, we need a TOC with links to readme files in all avail
Florian Effenberger schrieb:
I miss the plot on this - which readme are you talking about? ;)
Hi Florian,
we talk about THE readme.txt of each LibO build, with WIN I see it in
the readmes folder folder, in a Dev Builds it's the only readme.txt there.
CU
Rainer
Le 2013-01-27 17:10, bfo a écrit :
Hi!
My proposal:
e) a reminder at major version + automated closing of bug report after first
major.maintenance version if a reminder is last comment (which means no
activity)
This will give bugs cleaning every 6 months. Not a bad deal...
Most of bugs in NEEDI
Le 2013-01-28 08:13, Petr Mladek a écrit :
On Mon, 2013-01-28 at 10:05 +0100, Rainer Bielefeld wrote:
Petr Mladek schrieb:
This will cause many mails only in the first round. It will be normal
level of mails if we do this regularly.
Hi,
That's an illusion, total number of mails will always
On 01/28/2013 03:49 AM, Jean-Baptiste Faure wrote:
Hi all,
Please, could you try to reproduce the crash I described in the bug
report 59931 : https://bugs.freedesktop.org/show_bug.cgi?id=59931
For the moment I am alone who can reproduce this bug ...
Best regards.
JBF
Sorry, but LO 4.0.0.2
On Mon, 2013-01-28 at 10:05 +0100, Rainer Bielefeld wrote:
> Petr Mladek schrieb:
> > This will cause many mails only in the first round. It will be normal
> > level of mails if we do this regularly.
>
>
> Hi,
>
> That's an illusion, total number of mails will always be the the same.
> Only the
On Sat, 2013-01-26 at 14:27 -0800, Joel Madero wrote:
> +Assigning Bugs
> -AGREED: At this time QA team “pushing” bugs to developers
> isn't working, we will now only do “pull” philosophy (developers
> choose their own bugs and assign themselves
I suggest to add developers into CC for
Hi,
Rainer Bielefeld wrote on 2013-01-26 17:13:
Do we really need a copy of the readme on the site?
[..]
I also doubt that such copy is necessary. If we need it because of legl
reasons, we need a TOC with links to readme files in all available
languages and for all different public versions
Hi,
Markus and me have troubles to reproduce errors when importing Calc
documents into the last 4.0.0 builds. See
See https://bugs.freedesktop.org/show_bug.cgi?id=59916
Have you seen such a problem, please?
Best Regards,
Petr
___
List Name: Libreof
Petr Mladek schrieb:
This will cause many mails only in the first round. It will be normal
level of mails if we do this regularly.
Hi,
That's an illusion, total number of mails will always be the the same.
Only the number of mails per cleanup will be smaller.
BTW, I dislike the "noise" the
Hi all,
Please, could you try to reproduce the crash I described in the bug
report 59931 : https://bugs.freedesktop.org/show_bug.cgi?id=59931
For the moment I am alone who can reproduce this bug ...
Best regards.
JBF
--
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.
__
On Sat, 2013-01-26 at 15:06 -0800, Joel Madero wrote:
> On 01/26/2013 02:48 PM, Jack Leigh wrote:
> >> c) a reminder + automated closing of bug after some period of time
> >
> > +1 Something like automated closing after 3 months in NEEDINFO
> Response: From developer side, they'll see a MASSIVE inf
22 matches
Mail list logo
