Why updater does not advise newest LibreOffice Still?

I have LibreOffice 4.2.8 and I prefer to use the LibreOffice Still.

However I realize the newest version of LibreOffice Still is now the version 4.3.6. The 4.2 branch is supposed to have reach the end of life. Why am I not advise of the new version by the updater?

Is it a bug? Is it a conscious decision from the Document Foundation?

(- A conservative user who doesn’t want however to run an obsolete software)

The updater will only offer the most recent bug fix version within the current series. That is what update means in computer software. To obtain a version in a more recent series (i.e., going from vX.y to vX+1.y) is considered an upgrade. The updater does not cater for this. It is necessary to manually perform this type of change.

Fine. I understand the point. But it’s not obvious for the common user: it’s not the way most software updaters work.

From my personal view:

The 4.4.x series is “still rather fresh”. There were new features an reworked code introduced, and the bug fixing has not yet (4.4.1) sufficiently advanced.

You may, however, comb through the 4.4 release notes for features you urgently are longing for, and which might be a reason to go some risk living with an unfixed bug.

With regard to 4.2.8 I never understood for what reason it was offered as the standard “still” version for a long time. It contained a bug which, though not of great importance for every user, was reason enough to introduce an extra release (3.3.4) to get rid of it. I also would recommend to treat 4.3.6 as the best available STILL version.

Editing with respect to the comment by @Beizerno -

Again from my personal point of view: Don’t take it too serious. If you are not interested in details and in giving feedback simply shift to a new “branch of the second digit” when it comes near the end of its “lifecycle”. If you are missing features, however, visit the release notes for the series of releases to come and decide then whether or not its features are worth taking a risk as I told above. Even if you don’t like to go into details yourself, you will - as any human - at least have to decide of your own whom to ask for advice. Follow the TDF, follow me, follow someone else, overcome your dislike to worry about details … It’s your turn. Who should decide when time has come to shift to the next version of your car or to another whisky brand?

Thank you for the detailed answer.

But more generally, I’m still aware for the future: how can I trust the updater to give the version I need? Without having to spend time on forums to learn about it…

I too agree it would be a handy feature to have that the notification informs of either an update or an upgrade (easy for me the non programmer to say). In the mean time, at https://wiki.documentfoundation.org/ReleasePlan a detailed plan for all future versions is available (under the Publishing Date). One could add it to a personal calendar as a reminder.

I agree, would be better if there would be a notification if ANY new version is available. That is the exact purpose of updating … being up to date. When one is using a version 4.2.8 while there is a version 4.3.6 available in my opinion one should receive a notification of “newer software being available”. One could then visit your website and decide what to do. Although technically there might be a subtle change between an update and upgrade, one should keep in mind its purpose. I think most users just want to be up to date, not caring whether the new version is in the same branch or whether it is technically an update or upgrade.

Having said that … another question that pops to mind is … HOW are we supposed to update or upgrade? Can you install a newer version “over” an older version? Or do you first need to deinstall the older version? (and if so, will all my custom settings be saved?)

Your question would be a good question to ask as a stand alone question so it comes up in searches. By default the newer version prompts to install in the current version’s folder and will keep your settings, templates etc. You can install to a different folder to have the different versions side by side. I think someone has answered a similar question about this.