On Mon, Aug 13, 2012 at 12:49:41PM -0700, Joel Madero wrote:
> Can someone who has permissions (or if someone can give me permissions) to
> access http://www.libreoffice.org/get-involved/qa-testers/, we need to add
> the QA IRC channel (#libreoffice-qa) to the site.
done
__
Can someone who has permissions (or if someone can give me permissions) to
access http://www.libreoffice.org/get-involved/qa-testers/, we need to add
the QA IRC channel (#libreoffice-qa) to the site. Thanks all
Best Regards,
Joel
___
List Name: Libreoff
__
Florian Reisinger
Von meinem iPad gesendet
Sent via iPad
Am 13.08.2012 um 20:23 schrieb Joel Madero :
Excellent. You mind doing this monthly? We have 1,379 NEEDINFO bugs
currently.I feel bad closing so many when a lot of them are as simple
as attaching a document. Maybe once we get unconf
Excellent. You mind doing this monthly? We have 1,379 NEEDINFO bugs
currently.I feel bad closing so many when a lot of them are as simple
as attaching a document. Maybe once we get unconfirmed under control we can
move on to NEEDINFO and INVALID to see if there are some in there that we
can pro
Hi Joel!
__
Florian Reisinger
Von meinem iPad gesendet
Sent via iPad
Am 13.08.2012 um 19:06 schrieb Joel Madero :
Hey Rainer,
Do we have the ability to automatically close bugs + add comments that are
2+ weeks old with NEEDINFO status without any action by the user? This way
I, and others, don
Hi Pedro,
On Mon, Aug 13, 2012 at 09:54:15AM -0700, Pedro wrote:
> As an ex-QA member, ...
> Apparently this (time based release) development model works for other OSS,
> but I believe that is because they must have a much larger QA community...
Lets please discuss that constructively: Yes, we ne
Hi,
On Mon, Aug 13, 2012 at 10:09:48AM -0700, bfo wrote:
> This is of course apart from all other bug fixing and QA activity. Details
> to be discussed.
Yes, they will be. Please wait until Thursday -- I will present a proposal not
unlike that one to the ESC. We need to get the buy-in from the de
On Mon, Aug 13, 2012 at 09:38:21AM -0700, bfo wrote:
> I am starting to doubt that it helps. I recently delivered Windows bt to
> most crash bugs I could find. Prepared wiki page about it. Asked for review
> of that page. Silence. Few of the bugs were fixed, without any comment if my
> bt was usefu
Thanks Peter. Given the information you and Rainer provided I think the
best thing for QA triagers to do is to mark as WORKSFORME in most cases
unless they know specifically that the bug was fixed and then maybe CC the
person who patched the bug so they see the bug is closed. If this isn't the
best
Michael Meeks-2 wrote
>
> So - I like the idea of highlighting a small set of the most critical
> bugs each-week - say five; and having them linked in the ESC minutes
> with a small write-up. Of course that would need to be generated by QA.
> The bit that is unworkable in the above is
Hey Rainer,
Do we have the ability to automatically close bugs + add comments that are
2+ weeks old with NEEDINFO status without any action by the user? This way
I, and others, don't have to keep track of NEEDNIFO bugs so closely. If we
can do this, maybe do a weekly or monthly "purge" for these b
Joel Madero schrieb:
As most of you know we've started a major push to triage the unconfirmed
bugs and I am going to give updates periodically for 2 reasons
Hi Joel,
sounds great!
A small hint from my side: It's useless to change status for bugs like
"Bug 45124 - PRINTING: Problem with pri
Hi bfo
bfo wrote
>
> I would be happy if I achieve the change in base workflow - new feature in
> the codebase? Splendid! But unit tests, testcases and manual testing done
> before commiting. QA OKeyed the feature? Then you can commit.
>
As an ex-QA member, I think I should warn you that LO is
Michael Meeks-2 wrote
>
> The reason I graph regressions each week is to try to add focus there;
> if you can think of another more encouraging way - that'd be
> appreciated.
>
Hi.
Unfortunately those graphs are discouraging in many ways. Especially if one
thinks about upgrading LO...
Mic
Hi All,
As most of you know we've started a major push to triage the unconfirmed
bugs and I am going to give updates periodically for 2 reasons: 1. just so
we all know the progress :) 2. to remind people that we always need more
individuals helping out at least until we get a grasp on the 12+ mont
Hi there,
So - in the attempt to get something concretely actionable out of this;
I liked this idea:
On Sat, 2012-08-11 at 12:30 -0700, bfo wrote:
> Call for bugs (CFB). I think that CFB should be introduced in the release
> schedule (example http://wiki.documentfoundation.org/ReleasePlan
On Mon, Aug 13, 2012 at 11:02:49AM +0100, Michael Meeks wrote:
> > or rewriting filters just to introduce 12 regressions.
>
> Um - you think we re-write filters just to introduce regressions ? :-)
> If it's the RTF filter you're concerned about (the biggest re-write
> recently), it has remov
Hi Michael, all,
On Mon, Aug 13, 2012 at 10:36:27AM +0100, Michael Meeks wrote:
> On Fri, 2012-08-10 at 12:16 +0200, Timur Gadzo wrote:
> > I'm asking for EXPLANATION in the first post when will FIXES for bugs
> > resolved in MAB 3.5 be included in LO 3.6 CODE.
>
> Ah ! sorry, I mis-underst
Hi Sophie,
On Mon, Aug 13, 2012 at 11:14:34AM +0200, Sophie Gautier wrote:
> Hi all, Yifan,
>
> So after a long time (sorry for this long absence), I would like to
> come back to Moztrap and try to help to test it.
Welcome back :) Please let me know if you got problem of registration.
> My firs
Hi there,
On Fri, 2012-08-10 at 08:27 -0700, bfo wrote:
> Not at all. After reviewing >400 bugs (and counting)
That's good work :-)
> I could double 3.5MAB numbers in an instant.
Hey ho; it is no secret that there is really no shortage of bugs in the
product :-)
> Just see 3.
Hi Timur,
On Fri, 2012-08-10 at 12:16 +0200, Timur Gadzo wrote:
> I'm asking for EXPLANATION in the first post when will FIXES for bugs
> resolved in MAB 3.5 be included in LO 3.6 CODE.
Ah ! sorry, I mis-understood :-) so the generic answer to:
"when will XYZ bug be fixed
Hi all, Yifan,
So after a long time (sorry for this long absence), I would like to come
back to Moztrap and try to help to test it.
My first question, the most important for us, is there now a possibility
of localization for :
- the tests
- the environment
From what I see on the todo list Yifa
Hi,
Two points to this:
On Fri, Aug 10, 2012 at 09:57:56AM -0700, bfo wrote:
> > I dont think discussing this on a mailing list will help us find the
> > silver
> > bullet to the problems you describe. However, you are most invited to just
> > us
> > on the next QA Call on August, 23rd 2012 1400U
23 matches
Mail list logo
