Currently, when a new version of LO is announced, there is no way I can find of working out what the changes from the previous version are. For instance, I have recently been told that version 7.2.7 is available. How does this change from 7.2.6.2? It seems that only 2nd-level changes are documented as such. I suggest two modifications: 1: any change to the release note should say which version (sub-version, sub-sub-version etc.) it applies to. 2: the 'check for updates' box should include a link to the relevant page in the release notes.
Requested details are provided for incremental releases on project Wiki Here: https://wiki.documentfoundation.org/Category:Release you'll need to review both the RC1 and RC2 final build for applicable fixes, and the release specific notes for any new "features" being delivered. IMHO the Wiki format is sufficient for those who want to dig into the differences of the release builds. => Invalid
(In reply to V Stuart Foote from comment #1) > Requested details are provided for incremental releases on project Wiki > > Here: > > https://wiki.documentfoundation.org/Category:Release > > you'll need to review both the RC1 and RC2 final build for applicable fixes, > and the release specific notes for any new "features" being delivered. > > IMHO the Wiki format is sufficient for those who want to dig into the > differences of the release builds. => Invalid Thanks you for providing this link, of which I was completely unaware. That shows that my second suggestion - to provide a link in the 'check for updates' page is necessary. So I am reopening this.
We have a link to the Release Notes on the About dialog too. The update checker is not available on Linux (and macOS?) and wont be relevant with the currently introduced incremental updates aka MAR updater (added for 24.2 as experimental feature and set to productive in 24.8; see bug 159979 for the request to disable it). However, the plan is to have a website showing what's new. In a nutshell, I suggest to not put much effort into the updater. And by the way, it's very recommendable to keep your applications up-to-date anyway :-).
As there has been a slight misunderstanding, I will change back to unconfirmed while clarifying. This is not about the main release notes pages, but about these ones: https://wiki.documentfoundation.org/Releases/24.8.0/RC1
(In reply to Buovjaga from comment #4) > As there has been a slight misunderstanding, I will change back to > unconfirmed while clarifying. This is not about the main release notes > pages, but about these ones: > https://wiki.documentfoundation.org/Releases/24.8.0/RC1 Reasonable, but the Category:Release page is the better static landing, rather than a specific build. https://wiki.documentfoundation.org/Category:Release Unless we provide a "current.html" with link to "previous" (prev aka. Still) and "latest" (prev aka. Fresh)...
We discussed the topic in the design meeting. While it's not clear what could be interesting for average users in minor releases since those are mostly bug fixes, it wont hurt to have a link in the updater. Although this would be limited to Windows and systems without incremental update procedure. Volunteer are welcome to implement the request.