Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

On 04/25/2014 08:40 AM, Charles-H. Schulz wrote:
Hello Tom,

Le 2014-04-25 15:35, Tom Williams a écrit :
On 04/24/2014 06:09 AM, Tom Davies wrote:
Hi :)
These bug-hunting sessions can be a great fun.

It's only for a short time-period so you can find yourself racing
other people who are also new to it all.  Even if you know nothing
how to do it there are experienced people on-hand to help.  If you
know coding then that can even be an advantage because you avoid
embroiled in 'interesting' details.

Sometimes these competitions have led to prizes, such as netbooks and
things.  Bodhi Linux have such awarded a a few people netboks as top
prizes.  The QA team here did the same around a year ago.  I think this
time there isn't a prize but it's a good time to get in some practice.
Good luck all!
Regards from
Tom :)

Thanks for mentioning this.   :)    I think bug hunts are great, but I
need to ask this question:   how does the current backlog of bugs factor
in with these bug hunts?     I understand the bug hunts are great for
finding new bugs, but I've filed several bug reports, some of which have
been stagnant for over six months.

Well you're right, it is about finding new bugs (or previously fixed
bugs that may reappear) in the development versions. Actually, "old"
or open bugs get fixed at every new release, while others get
(unfortunately) introduced. That's the factor you were asking about I

Not really.  I was asking how current backlog bug reports factor in with
these bug hunts.  As bugs are fixed in each new release, those bug
reports are eventually resolved and maybe even closed. They might be
reopened if a regression occurs, but that's something different.   I do
understand the need to find out if new features and functionality either
have problems, themselves, or possibly caused regressions but a
regression is a break of something that previously worked.   A bug
report that's still in "New" status, like my sample bug, hasn't been
fixed and my question is:  during these bug hunts, is there any effort
put into seeing if any of the backlog bug reports have also been fixed
or is the intent mostly to focus on the "new stuff," making sure new
features and functions work properly and to see if any regressions have
been introduced.

Here is an example:

It's not really stagnant. As I read on the bug reports comments, you
filed that bug against the 3.6.2 version. This version is obsolete;
but someone actually tested the problematic behaviour with a 4.2.0 and
the bug was no longer observed:
"So even it is not informed here, it is solved for the releases in

So it was fixed somehow. Please keep in mind that bug fixes are only
brought to actively supported versions (the ones you can download from
the website), not obsolete ones like the 3.6.x branch.

Yep, release 3.6.2 is certainly obsolete but that's the version of the
software in which I first experienced the problem.  I certainly hope bug
reports filed against *now* obsolete releases aren't being ignored.   
As for the status of my sample bug report being changed to "invalid",
I'm addressing that now since I experienced the same problem with Writer
4.2.3 on Windows XP.   :)

I'm excited about LibreOffice 4.3's release because the software keeps
getting better and better.  However, it's also a bit frustrating when
reported issues exist for a long period of time.

I hope I have answered your question;of course there are always
unresolved issues that are still in the actively supported versions.
Devs try hard to squash these bugs, and are very successful at doing
that, but there are always some leftovers.

Yes, you have and I appreciate your response.  :)








On 24 April 2014 12:19, Italo Vignoli <>

The Document Foundation (TDF) announces the schedule of the first
LibreOffice 4.3 bug hunting session, which will start with the
availability of the first beta of the new major release in calendar
21 (May 23 to May 25).

Participating will be easy. Details of the bug hunting session are on
TDF wiki
where there is also a growing list of LibreOffice 4.3 new features and
improvements to check for bugs and regressions

To participate, it will be necessary to have a PC with Windows,
MacOS or
Linux, and LibreOffice 4.3 Beta 1 (available at, plus a lot of enthusiasm.

Filing bugs will be extremely easy, thanks to the help of experienced
volunteers who will be around on the QA mailing list
( and IRC channel

A second LibreOffice 4.3 bug hunting session will be organized - with
the same pattern - immediately after the release of LibreOffice 4.3
Release Candidate 1, in mid June.

Short link to TDF blog:

Italo Vignoli - The Document Foundation
mob IT +39.348.5653829 - mob EU +39.392.7481795
sip - skype italovignoli
hangout / jabber
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0

To unsubscribe e-mail to:
List archive:

/When we dance, you have a way with me,
Stay with me... Sway with me.../

/When we dance, you have a way with me,
Stay with me... Sway with me.../

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.