Hello Florian and others
Let me point out what matters. It's not that simple that I'm "one of
many applicants that's unhappy because a single one is selected". It's
that I was alrady doing the majority of items for years prior to
selection topping in QA reports and still someone else was chosen
*w
Hello fellow QAers
Along my LO time, I saw many folks coming and some disapearring
(wondering why). Now I was faced with that, I decided to send this
message, to explain why it makes no sense for me to be in QA team
anymore (1).
I was OO user and casual bug reporter since 2005, and then LO user a
On Thursday, January 28, 2021, Florian Effenberger <
flo...@documentfoundation.org> wrote:
>
> William Gathoye (LibreOffice) wrote on 27.01.21 at 18:22:
>
>> Right now: 6.4 is EOL'ed[4] but it is still advertised on the website
while the update service is redirecting users of 6.4 to the 7.0 version
It's done already. It's manual and tedious now.
I always wonder if it takes a script or new Bugzilla version to have a
single button for BZ admins.
And some more, like "see all reports by that commenter", "see all commits
by that dev".
Buovjaga, you follow BZ, is there any chance ?
Regards
On
Hi
Thank you for your offer.
I guess Xisco will prepare QA report for 2018., ss discussed before,
so you may use that. Address is
https://qa.blog.documentfoundation.org/category/reports/.
Out of total number of fixed bugs it's important to know the part for
regressions because the rest is a real
Hello
Nice reports.
I hope you'll prepare yearly report for 2018 including also an
evolution for total number of open bugs and closed bugs.
QA blog page is narrow, it should be broadened. At least to the width
of blog.documentfoundation.org.
Best wishes in 2019.
Timur
___
Hi
Bug 57418 is on the list because last 3 messages were from
qa-ad...@libreoffice.org.
So not some malware, simply bugs without feedback.
On 8/14/17, Xisco Fauli wrote:
> Hello,
>
> Today I modified this script [1] to check those bugs pinged more than
> once with this message[2] and I've found
Hello all
I'm confused with all those Meta bugs. Looks like there are so many of
them that I wonder how that can help. I wasn't here on the list so I
don't know if that's explained somewhere.
In my view, we don't need them like that, and similar bugs can be
found by search.
Meta should gather hot
on for QA: Do these pages influence some decisions? Are
they still relevant? There should be some explanation.
Regards
Timur Gadzo
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://list
> On Thu, 2012-08-09 at 15:27 +0200, Timur Gadzo wrote:
>> I find that there should be an explanation in MAB 3.6. when exactly
>> will fixes for bugs resolved in "LibreOffice 3.5 most annoying bugs"
>> be included in LO 3.6.
>
> Right; that's not c
ReleaseLifecycle.png?
Regards
Timur Gadzo
-- Forwarded message --
From: Florian Effenberger
Date: Wed, 08 Aug 2012 12:24:47 +0200
Subject: [tdf-announce] The Document Foundation announces LibreOffice
3.6 with a wealth of new features and improvements
To: annou...@documentfoundatio
11 matches
Mail list logo
