On Thu, Jun 9, 2011 at 6:38 PM, plino <pedlino@gmail.com> wrote:
Can someone tell me if the daily named rc1 will be installed as a Dev or
overwrite my Stable 3.3.3RC1?
Since LibO-3.4 Final has been released, I would suggest 3.4.
According to the website, it will not overwrite the older version; however,
it was not easy to find when I installed it on Debian Squeeze (stable). I'm
still using LO-3.3.2 (build 202) with no problems. LO34 seems OK but there
were some issues mentioned in the Release notes which led me to keep using
3.3.2. Your mileage may vary.
I'd wait a few weeks before upgrading unless you have no mission-critical
documents to handle.
saludos,
Richard.
--
View this message in context:
http://nabble.documentfoundation.org/Release-dates-versions-tp3040743p3046545.html
Sent from the Discuss mailing list archive at Nabble.com.
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be
deleted
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
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.