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

Hi Tom,

I will try to rephrase it... Fresh is going to be renamed to Still (Stable) after a while. Bugs not 
found in Fresh will land in Stable within 6M... So the quality of the Stable will decrease if less 
people use the Fresh branch... So we need to find bugs early in the cycle ( when it is in the Fresh 
 " state" (even better in the RCs and Betas before it is the Fresh release)). Developers need time 
to fix bugs, so it would be ideal to work with a daily build from time to time to ensure the 
correct function there (daily build is from master branch). ( sorry, I am involved in QA. I "do not 
care" if a user is able to submit a bug, we have so many bugs to take care. It is important that 
more advanced users (who know what a Bug in a software means) uses the Fresh branch. I just want to 
point out, that we have many bug reports, when we release a "Fresh" branch and that the feedback is 
more valuable at the beginning of the life- cycle then at the end....

Sorry that this resulted in one paragraph (typed from iPad).... To cut it short: We need early 
feedback in order to have time to improve the software quality.... I hope I was able to carry 
across _my_ point... (I know, from a marketing prospective not perfect ;) )... If not, please ask :)

Liebe Grüße, / Yours,
Florian Reisinger

Am 06.08.2014 um 19:17 schrieb Tom Davies <>:

Hi :) 
That kinda assumes that new users are able to post bug-reports and that they want to do so.  

Most new users who run into a problem probably don't know how or can't be bothered or don't see 
why they should.  They might not realise it is a bug and just assume that it's the type of 
shoddiness that free things are likely to have or that they have broken it.

It really depends on how keen we are to have countless people bad-mouthing us and never trying 
LibreOffice again because of all the bugs they encountered (and probably never told anyone 
about).  People outside of LO keep telling me long lists of problems they encountered and why 
they wont ever try LO or anything like it ever again.  Usually their gripes are things that just 
don't happen in "Still" branch = yet because they were pushed into using the less stable branch 
we now have someone(s) happily telling everyone to avoid LO because it's @*#p

If we were clearer about the purpose of each branch then probably countless people would still 
try the "Fresh" branch anyway, but they would be happier about it if they did find a bug.  People 
often want to help and repay LO for being fantastic and if they saw such an easy way to help it 
might even boost the numbers of people actively testing early releases!  

Regards from 
Tom :)  

On 6 August 2014 18:01, Florian Reisinger <> wrote:
Hi Tom,

If we do not find the bugs in the fresh version, they won't be resolved until the rename to 
Stable/Still. If less use Fresh, the quality of the next stable will be lower.... Does this help?

Liebe Grüße, / Yours,
Florian Reisinger

Am 06.08.2014 um 11:17 schrieb Tom Davies <>:

Hi :)
This seems to be contradicting what Charles is saying.

Also is it really a good policy to force new and unwitting users to act as guinea-pigs?  
Should all new users be pushed into finding and fixing bugs?  Would it really be bad to give 
them a clear and easy route to a less buggy version?
Regards from
Tom :)

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.