Bug 149400

Summary:	Provide more detailed info about versions in release notes
Product:	LibreOffice	Reporter:	Peter Toye <lo>
Component:	Documentation	Assignee:	Not Assigned <libreoffice-bugs>
Status:	REOPENED ---
Severity:	enhancement	CC:	olivier.hallot, vsfoote, xiscofauli
Priority:	medium
Version:	7.2.6.2 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:

Description Peter Toye 2022-05-31 11:14:41 UTC

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.

Comment 1 V Stuart Foote 2022-06-01 05:07:38 UTC

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

Comment 2 Peter Toye 2022-06-01 10:38:41 UTC

(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.