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

Hi :)
Just to deal with just 1 of those points ...

There is an archive of older releases so people can download out-of-date
versions if they want to.

It's not widely publicised (to avoid confusing people) but when people ask
this mailing list, and presumably other forums too, someone does inevitably
point them in the right direction.  It's also possible to find out from the
archives or by searching the site.

Regards from
Tom :)

On 10 October 2014 18:36, alphacrash <> wrote:

 Please can we move on...  Charles S. (aka Tanstaafl) was given
instructions and has agreed to do what needs to be done and review the
corrected function for his use case with a current build of  master
(4.4.0alpha0+)--and respond in the fdo#76565 BZ issue regards the UX

Every thing else is just hubris or a poor understanding of the project's
timed release development flow.  Please let it go--most users on this ML
have NO interest in this thread other than the drama. -- Stuart

Actually, this type of discussion points to a process issue.  I imagine it
is one of the reasons for having this site.

It's obvious the functionality list of Libreoffice is becomming
overwhelming.   The issue of lost functionality upon which user's have come
to rely combined with the unavailability of previous versions on the
Libreoffice website affects LibreOffice across the board.   One can
with the question for the motive for this.

Regardless of the outcome of that discussion,  *there is  a potential HUGE
conflict of interest looming on the horizon in the form of creating bugs so
that outside companies can charge $$$ to fix them. *

 Does there exist a set of LibreOffice TEST documents that are designed to
test ALL OF THE FUNCTIONALITY of a given version of LibreOffice?
Specifically, one that can automate test, perhaps through macros or self
contained programs, all the functionality of Libreoffice?

SUGGESTION #3:  If such a set of documents or test harness does NOT EXIST.
Perhaps the QA team could itemize all the functionality of a version of
Libreoffice and structure a project for contribution by end users to
contribute the tests.  i.e:  A test suite that each useer could download
then run and/or contribute more.

SUGGESTION #4:  If a test harness is too complicated, could the QA team
an itemized list of all the functionality of LibreOffice, inherited and
otherwise *and create some sort of method to crowd source the testing in a
manner designed to capture any lost functionality*?   i.e.:  a project
website for each version LibreOffice with the 100,000 things that
LibreOffice can do where the users can test each one and report the test?

NOTE:  This is different than just putting a new version out and seeing who
gets hurt.  Remember, not all people live in countries where employers have
to make a case to the government for firing a person.  Yes, there are
of disclaimers on the software, but the current process may end up making
LibreOffice the sofware you use only for NON-CRITICAL documents.  The
long-term user base effects should be obvious.


View this message in context:
Sent from the Users mailing list archive at

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

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.