It might be helpful to have an two entries "New Features" and "Recent Fixes" in the "Help" menu below "About LibreOffice" linking to:
respectively. This might help explaining the changes in a x.y+1.z update (new features) vs. a x.y.z+1 update (bugfixes) in addition to give people more visibility to later at all esp. for those using distros or the updater, who never see the PR announcements for the updates.
Valid enhancement request. Would be useful -> NEW
I support the idea, however :
(In reply to comment #0)
As it is now, this page provides far too little real info, anyway, if the goal is to inform users on features.
This would then benefit from a pointer to e.g. /4.2.4/RC1 and/or general release plan information.
(In reply to comment #2)
> I support the idea, however :
> (In reply to comment #0)
> > http://www.libreoffice.org/discover/new-features/
> As it is now, this page provides far too little real info, anyway, if the
> goal is to inform users on features.
That would be an update of the webpage, which sure would be nice in addition, but is beyond the scope of this bug.
> > https://wiki.documentfoundation.org/Releases/4.2.4/RC2
> This would then benefit from a pointer to e.g. /4.2.4/RC1 and/or general
> release plan information.
Yeah, either transcluding the RC1 fixes or having one 4.2.4 page with "fixed in rc1", "fixed in rc2" ... sections would be nice. As the delta on rc2s is sparse anyway, this might be a good idea general. But again, that is mostly independent of pointing towards these infos from the program being useful as a start.
So ... lets not feature creep this ;)
I personally would vote against this. At least right now both these links are pretty much useless from user perspective.
I think this would better suit to help landing page in wiki, a new section "New features in 4.5.x" (changing according to your version).
Would have to agree with Cor and mahfiaz that the links unfortunately dont provide enough useful info from a user's perspective.
Please add keyword 'needsUXEval' and CC 'firstname.lastname@example.org' if input from UX is needed.