Bug 139773

Summary:	Online Update: add a checkbox or a slider for version to use (ex. just Still)
Product:	LibreOffice	Reporter:	Noah <bugzilla>
Component:	Installation	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	enhancement	CC:	aron.budea, ataronchronon747, bugzilla, heiko.tietze, kendy, stephane.guillou, thb, vsfoote
Priority:	lowest
Version:	Inherited From OOo
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=48369 https://bugs.documentfoundation.org/show_bug.cgi?id=97302 https://bugs.documentfoundation.org/show_bug.cgi?id=149838
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	113339

Description Noah 2021-01-19 22:53:34 UTC

Description:
add a checkbox or slider which version to use.
the latest or the slightly older.

Actual Results:
no checkbox

Expected Results:
some checkbox or slider to choose which version is wanted.
the update system should only check for that version


Reproducible: Always


User Profile Reset: No



Additional Info:
I don’t use LibreOffice for the moment because it lacks several functions I like.
I don’t have a “Help - About LibreOffice”.

Comment 1 Timur 2021-01-20 07:51:23 UTC

I guess this is for Update checker. Please explain better what you want with example versions. looks like WontFix so far.

Comment 2 Noah 2021-01-20 11:44:29 UTC

Mozilla Firefox has the release and the ESR version.
When using the ESR version, the update system checkes only for ESR.
When using the release version, it only checkes for release.

I used LibreOffice years ago, but didn’t find the setting to choose the “ESR“ version of LibreOffice.
If I remember correctly, it was called LibreOffice Still.
The other one was called LibreOffice Fresh.
I want only the Still version.

Comment 3 Heiko Tietze 2021-12-06 10:05:31 UTC

An update to the updater is currently in discussion. If bug 54242 becomes implemented we do not need to decide whether to include still/fresh.

Comment 4 Aron Budea 2021-12-06 12:42:26 UTC

This is actually how the update check currently works. It's described in bug 97302:

========
Only if the micro version (the third digit of an available fresh version) is larger or equal the micro version of the installed still version will the user be offered the fresh version:

installed still | available fresh | available still
x.y.z           |  x'.y'.f        |  x.y'.s

f >= z → fresh update will be offered
f < z and x.y'.s newer than x.y.z → still update will be offered

otherwise the response will be "up to date/no update available"

however it is unlikely to ever reach the f >= z condition with the release schedule when a user regularly updates.
========

Ie. with the still version almost always the still version gets offered.
Ohter practical purposes are covered in bug 97302 I'd say.

Comment 5 Stéphane Guillou (stragu) 2024-06-24 08:57:19 UTC

*** Bug 153101 has been marked as a duplicate of this bug. ***

Comment 6 Stéphane Guillou (stragu) 2024-06-24 09:02:03 UTC

Note that for Windows, we now have MAR-based incremental updates: https://wiki.documentfoundation.org/ReleaseNotes/24.2#Core_/_General
(experimental in 24.2, not experimental in 24.8)