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

Am 06.08.2014 07:29, schrieb Pikov Andropov:
Florian Reisinger wrote on 8/6/2014 1:22 AM:
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 
So yes, we have a different model, so we need different names then the standard :)

What are the differences between the two branches?

The younger one (fresh) has been forked later from the master development
branch. Therefore it obviously has more features.

But as it is younger, it is less "mature" than the earlier (still) branch.

If you look into each branch separately, the branch goes through the well
known states (alpha, beta, RC, final) for its first release (the x.y.0), but
then keeps iterating through several additional (bugfix) releases, from
x.y.1 to x.y.6 in most cases. So each branch individually gains increasingly
bugfreeness during its individual


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.