I currently am running 4.0.4 on all my systems - Ubuntu and Windows.
Currently, in the pas month, versions 3.6.7 and 4.1.0 have come out.
3.6.7 is the end-of-line release for that line and it very stable, but
does not have some of the features of the 4.0.x line.
4.1.0 is the first of that line and has some features that 4.0.4 does
not. These include better MS XML filters to read/write the file formats
like .docx and the others with "x" in their name.
If you follow the information in the release plan image [link] then you
may be happy.
https://wiki.documentfoundation.org/File:LibOReleaseLifecycle.png
For some people, they wait till the release ends with .4 or .5.
i.e. go from the 4.0.x line when you reach 4.0.4 or 4.0.5
Then go to the 4.1.x line when 4.1.4 or 4.1.5 comes out.
4.0.4 is out now and 4.0.5 comes out in about 2 weeks.
3.6.7 is also out now, but I would stick with 4.0.4 and its newer
versions, for now.
On 07/26/2013 05:31 AM, la10497@iperbole.bologna.it wrote:
Unfortunately, the "3rd digit rule" doesn't work as goog as expected...
I use report builder in base, 4.0.3.3 version. Download 4.0.4 and
report builder no more works (crash in opening).
thanks anyway for developers work, I remember this is a free sw, at
the
end....
Federico Quadri
Tom Davies <tomdavies04@yahoo.co.uk> ha scritto:
Hi :)
That 3rd digit is roughly the equivalent of "Service pack". So
usually the higher it is the more stable it is. Of course even just
bug-patches and fixes can sometimes introduce unexpected problems
that might not get caught by QA.
The best answer, imo, is to keep a very stable version that you are
happy enough with on all the machines you look after especially ones
that have limited access or that you can't reach easily. Then on 1
machine find some way of being able to test-drive an occasional
beta-test versions before it gets released. Preferably do about 1
per branch. The problem is that things you might care about deeply
might not even be getting used by other people at all. So it's only
you that might notice. So if you didn't test-drive then the problem
might never be found. Also it's better to do your testing on a beta
release rather than a full release because it's during the early beta
stage that the most devs are the most focussed on the 1 single
version and trying to solve the most problems quickly. Also it's when
the fewest other people are making bug-reports.
There are various ways you could make sure you have access to 1
version for use for work that has a dead-line and another version
that you can just use to try things out and make sure it all works.
Regards from
Tom :)
________________________________
From: Amit Choudhary <contact.amit.choudhary.india@gmail.com>
To: "users@global.libreoffice.org" <Users@global.libreoffice.org>
Sent: Friday, 26 July 2013, 3:35
Subject: [libreoffice-users] 4.0.3
Hi,
I was using 4.0.2 and then I downloaded 4.0.3 but 4.0.3 is not as
stable as
4.0.2. So, now I am downloading 4.0.4.
I am more interested in stable and feature rich (optional)
software rather
than frequently released software.
Stablility is very important because a non-stable software /
software
having many bugs results in loss of time and frustartion.
Amit
--
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.