Here in QA, we always repeatedly prompt users to use the latest available builds before opening a bug report, because they don’t know that we only provide support (or “assistance”, as some people at TDF misguidedly want to call it. Pfffft, call a spade a spade) for the latest build at any given time.
The text could say something like this: “This build is now out of support. Upgrade to the newest available version to get the latest bug fixes.”
I suppose that such a prompt would be considered very intrusive. I'd say, it would be OK if shown as static text on About dialog (yes, only discoverable if user decides to look there; yet, when filing bugs, users are expected to visit the dialog to get the version information ...)
To follow on your idea, Mike, it could be a link like Mozilla Firefox does, to avoid putting a lot of additional text to the dialog.
│Version: Major.minor.bugfix.build (U͟p͟g͟r͟a͟d͟e͟ ͟f͟o͟r͟ ͟t͟h͟e͟ ͟l͟a͟t͟e͟s͟t͟ ͟b͟u͟g͟ ͟f͟i͟x͟e͟s͟)│ └─────────────────────────────────────────────────────────┘
I like the idea of the extra message in the About dialog when:
- A bugfix version is available
- The version has reached EOL, prompting to upgrade to the current Still version.
But keep it separate from the Version Information block as we don't want to copy that extra text.
The "Help > Check for Updates" dialog could be improved in that regard too. Currently, when someone is using an EOL version, the message is of the type:
> LibreOffice 7.4.4 is available.
> The installed version is LibreOffice 18.104.22.168.
It could clarify the fact that 7.2 will no longer see releases.
Regarding notifications, I guess a one-off balloon that says "7.2.7 is not supported anymore, we recommend upgrading to <current still version>" could be added without being too naggy?
Wouldn't it be even great if users would be automatically updated/upgraded?
I mean, we already have a dialog for auto-updating
(that does not work in anyway and is, IMO, giving a very negative image about the product - it's 2023!)
So why not put some effort in that and get this work finished?
I believe it's a lot of work, but from it we could:
- Get most users on the latest version (that would eliminate old bugs being reported)
- It would help getting the "business" version even more tested and stable
- It would provide all that a regular user is already expecting from a 2023 product (every piece of software i use auto-updates itself except for LO)
- (Other advantages...)
I'm not seeing anything in Bugzilla about this:
I had LibreOffice_7.3.2_Win_x64.msi installed, with a nasty problem of the text import preview being invisible in dark modes. For months I checked Help -> Check for Updates, and it always told me none were available.
I happened to see a note in the Fediverse, went to your website, and found LibreOffice_7.5.0_Win_x86-64.msi - with my problem beautifully fixed! And a _way_ better dark mode!
Was there some glitch in the update check? Is it fixed now? Obviously I won't trust it for awhile...
(In reply to Loren Amelang from comment #5)
> Was there some glitch in the update check? Is it fixed now? Obviously I
> won't trust it for awhile...
No glitch! The thing just... never worked!
(but don't talk too much about it... or someone will just tell you to shut up :(
I believe that, in addition to a more "permanent" reminder somewhere non-intrusive (e.g. in the About Dialog), we could consider a one-time intrusive prompt (which, if dismissed, never comes up again) - when LO determines that updating is important (whatever that criterion might be).
Well, possibly this could be combined with the existing upgrade prompt then? Before EOL, it could simply offer an update; after EOL, the balloon tip could include the EOL notification.
Showing an information like
You are on the latest version, find <a>nightly builds here</a>
(maybe pointing to developer versions is too much)
The latest public version is <a>22.214.171.124</a>
sounds reasonable. But I wonder if we should add the link to TDF since the application might be installed via app store, package manager keeping it intentionally "stable", or provided from a third party.
(In reply to Heiko Tietze from comment #9)
The upgrade prompt already is conditional, and it is disabled in distro repos. If not combined into the prompt, we could still reuse the same branding info.
We discussed the topic in the design meeting.
We do show the info in the (auto-)updater on Windows, and Linux repositories prefer their own schedule. Plus, the About dialog is not an incentive per se and probably not what users expect.
However, it might be good to inform users beyond this and show an infobar when a new major is available. The text could be "This version is no longer supported" along with buttons "Update", "Show again", Don't bother again".
> The text could be "This version is no longer
> supported" along with buttons "Update", "Show again", Don't bother again".
And what will happen when a user presses "Update" button on windows?
- Will it get you to the download page?
- Or will it start an update process (download+install)?
Users would surely expect the last!
But there is no foundation for that to happen (and apparently no will either) - see bug 54242