Bug 139773 - Online Update: add a checkbox or a slider for version to use (ex. just Still)
Summary: Online Update: add a checkbox or a slider for version to use (ex. just Still)
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: lowest enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Updates
  Show dependency treegraph
 
Reported: 2021-01-19 22:53 UTC by Noah
Modified: 2021-12-06 12:42 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.