On 02/01/2013 at 16:45, Pedro <pedlino@gmail.com> wrote:
" Pre-releases
Below, you can download a pre-release of the next version of LibreOffice
for evaluation, QA testing, etc. These versions are not meant for general
use."
It does not say that the currently available build is a BETA
But it says that this is not stable, it is for "testing" and it is NOT "for
general use". These are most important information here.
If user just want to download app, then he want to know where is stable
release. Why do you think that TDF should force users to know anything about
software release process and differences between alpha, beta and release
candidate builds? As long as these are "not for general use", most people
don't care.
And people who do care - well, they can get information and links to certain
builds elsewhere (like TDF wiki).
I don't see a point in cluttering download page with irrelevant information.
People already have problems with choosing right version and finding download
link. Creating more complex descriptions won't help them.
--
Best regards
Mirosław Zalewski
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.