No changes noted on update prompt

English
#1

I get the “LibreOffice has a new update” prompt, I click it, then I get a window noting the new version number, but not what else is different about it, as in changes or new features etc, as in why I should update it.

image

I know of course I should update for security or compatibility reasons, but sometimes I run an update blindly and things get worse. So, why aren’t changes (a changelog or release notes) on the update box?! This seems like a minimum. Now I have to go hunt it down, if I’m even getting the terms right.

#3

Why do you ask this question users of LibreOffice. Nobody has any clue of the preferences of LibreOffice developers. In other words: You need to file an enhancement if that is an important feature for you to avoid calling Release Notes - The Document Foundation Wiki

#4

When you click Download... button, you get to main LibreOffice download page. It contains links to major version release notes; and it also contains links to specific changes done in the minor releases - if you navigate to DOWNLOAD|Release Notes page from there.

Why would you need another set of links in the dialog, when you get everything from the download page?

1 Like
#7

@Opaque You’re not helpful, I’m posting here because the box should note the changes or have a link to them. I found the changes by doing a Google search for the version number. That shouldn’t be required of the user. The box should note the changes or have a link to them. I posted here because a Google search brought me here when I looked for where to post an issue with LibreOffice. This website is of course called “ask”, so that’s what I did. I have no idea if it’s only users here, but someone else did help.

@mikekaganski Thanks, but there was no indication that Download would merely take me to a page to click another Download button which also contained the release notes. The box should either have the release notes, or an obvious link to them. “Download” is not labeled “Check release notes here”

#9

Oh lol. Of course, how could one ever try to look at the project’s home page for ways to file an issue on that project! That’s just unthinkable! Of course, Google knows better.

Please do file a bug report suggesting to add a note about release notes being available on the download page accessible using Download button.

#2

Never upgrade the LibreOffice blindly. Read the descriptions of the new versions,
https://wiki.documentfoundation.org/Releases/7.1.5/RC1
https://wiki.documentfoundation.org/Releases/7.1.5/RC2
… and/or try it by “installing” a portable version of the new version (on Windows).
https://portableapps.com/apps/office/libreoffice_portable
A portable version have not bother the actually installed version.

#5

Thanks, but the issue is the Check for Updates prompt shows a new version number but not what’s different about it. I don’t know where else to post about that issue. Checking a website for those changes doesn’t add those changes to the Check for Updates box, which doesn’t even have a link to the changes. The changes or a link to them should be in the box.

#8

The Changes list sometimes is a huge list. In case 7.1.5 version contains “only” 55 items relative to the previous (7.1.4) version. (45+10 in the RC1 and RC2 release candidated versions).

It is not a good idea to show all of the changes in an older version, because when somebody will upgrade from a more older (for example 6.1.6) version, he/she will not see all of the changes between the actual and the latest versions. A cumulated list (from the actual to the latest) would be a more huge list.

And there are not lots of webpages what contain cumulated lists of “ALL OF THE CHANGES from a specific version to the latest version”.

And you know the URL now, where you can check the changes - if you want it. Just change the version number in the URL, if you want to see the changes of an another version. Always exists a RC1 version, but sometimes only the RC1 exists, but not RC2, RC3, etc. versions…

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.