Bug 155885 - Check-for-update in nightly build should suggest newest nightly
Summary: Check-for-update in nightly build should suggest newest nightly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Updates
  Show dependency tree / graph
 
Reported: 2023-06-16 23:03 UTC by Eyal Rozenberg
Modified: 2024-06-23 12:43 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2023-06-16 23:03:53 UTC 
If I use a nightly build, a newer nightly is available, and I check for updates - I expect to be offered to upgrade to that newer nightly. Yet - I am not.

Bike-shedding: If a version is released, the offer could be either to upgrade to the latest nightly, which has a new version number, or to the release with same version number. Not sure which is the better idea - but please choose one.
Comment 1 Stéphane Guillou (stragu) 2023-06-19 08:43:37 UTC 
That makes sense to me. Currently says "LO is up to date".
Xisco and Cloph, thoughts from a QA / Infra perspective? If on a master build, what should happen when passing branch point?