This seems to contradict what both Charles and what Florian Reisinger
It does seem to make more sense though. It kinda explains why people
prefer one branch or the other one, which was very unclear from Charles
It also kinda explains the graphic on the;
page, although that graphic doesn't make a lot of sense to me. Do
people understand it? There used to be a neat little graph which kinda
boggled the eyes at first but began to make sense after staring at it
The bit about "master branch" was a bit beyond me but suggested an
to the older thread about how bug-fixes added to the older branch
get into the newer branch. Still i am sure i am not the only one
by such a thing.
So Nino's answer suggests that some people might prefer the branch that
matured because by that time it is more stable. So releases with a
3rd digit are more mature, more stable and less likely to have
The only downside is that you get less features.
Then it also makes sense that people would often prefer to use the
less mature branch even though it hasn't had as many bug-fixes added to
However this seems to contradict what Charles was saying about both
branches being fully stable. So which is wrong?
On 6 August 2014 09:42, Nino Novak <firstname.lastname@example.org> wrote:
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
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
> What are the differences between the two branches?
The younger one (fresh) has been forked later from the master
branch. Therefore it obviously has more features.
But as it is younger, it is less "mature" than the earlier (still)
If you look into each branch separately, the branch goes through the
known states (alpha, beta, RC, final) for its first release (the
then keeps iterating through several additional (bugfix) releases,
x.y.1 to x.y.6 in most cases. So each branch individually gains
bugfreeness during its individual
To unsubscribe e-mail to: email@example.com
Posting guidelines + more:
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
Impressum (Legal Info)
: 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