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


Hello Pikov

On 6 août 2014 07:29:17 CEST, Pikov Andropov <pikov22@gmail.com> wrote:
Florian Reisinger wrote on 8/6/2014 1:22 AM:
Hi,
The problem we have: We do not have one release branch as Firefox
has, we have two... Users should use and find bugs on the "Fresh"
version in order to make thee fresh, which will be renamed to stable
after 6M.
So how to say "you can use the feature packed fresh"? It is not an RC
it is an tested final release....
So yes, we have a different model, so we need different names then
the standard :)

What are the differences between the two branches?

basically one has more features than the others. They are both stable (hence the change of name) 
but are in a different state and started at a different date. It is very much like MS Office 2011 
and 2013 or a car model with a  different serie each year.

You can get the abridged and detailed list of features and bug fixes for each version by reading 
the release notes.

Cheers,

Charles.
-- 
Envoyé de mon téléphone avec Kaiten Mail. Excusez la brièveté.

-- 
To unsubscribe e-mail to: users+unsubscribe@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.