________________________________
From: Steven Shelton <steven@sheltonlegal.net>
To: users@global.libreoffice.org
Sent: Thu, 30 June, 2011 15:19:56
Subject: Re: [libreoffice-users] Re: SubForms and Photographs in LO Base
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/30/2011 11:12 AM, Davide Dozza wrote:
I'm confused as to why 3.4 is labeled as "Final" on the site, but
it's "not recommended for production use". What gives? Is this
"final" really an RC?
Because it's the development branch.
Oh, so we're moving to "even-numbered releases are development,
odd-numbered releases are stable"? Is that it?
If so, something probably needs to be said about this on the website
to clarify it for end users.
Steven Shelton
Hi :)
There is a yellow warning triangle and exclamation mark ! beside the 3.4.x
series/branch. Also it firmly says "For early adopters only". The 3.3.x
series/branch has a big friendly green tick and words saying that it is the
stable branch. It could be a little bit clearer but i'm not sure how lol ;)
Don't worry, lots of people miss those details too.
Regards from
Tom :)
--
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
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.