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


Hello,

it is confusing, when the most stable version does not compile, as it happened to me, and when this 
is not going to
change.

I suggest recomending only versions, which either compile, or in case they don’t compile, they are 
supposed to be
publically tweaked to compile.

Regards
  Дилян

On Wed, 2019-01-16 at 12:03 +0000, Kaganski Mike wrote:
On 16.01.2019 14:49, Дилян Палаузов wrote:
Hello,

what I wanted to ask was, why does the LO-webpage recommend for enterprises end of life 
products.

My understanding of the processes is, that there are usually a stable version, that is not 
end-of-live, and a most
current version, at the same time.  However there are gaps, when the webpage offers only one 
version, that is not end of
life, without stating this clear.

6.0 *is* the stable version at the moment, that is rightfully 
recommended now. EOL means only one thing: no more releases for this 
branch are planned. This happens at the moment when the last release of 
the branch comes out. The last release for 6.0 brought last portion of 
the fixes; and at this moment, 6.0.7 is considered the most stable - and 
for that reason, recommended; and at the same time, TDF won't release 
any more patches to it - so it's EOLed. So do you suggest to only 
recommend versions that don't have the last pack of fixes?

-- 
Best regards,
Mike Kaganski


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.