PR#4492 (updates for upcoming release) Review - suggestions

[flo91]

This are just some suggestions for improvements in the course of a review for the PR #4492.
As that PR was already merged, I decided to publish my suggested changes as a new PR.

Review:
The content of the documents looks really good. 👍🏻
I could not find a thing that is unclear or hard to understand, esp. after including the suggestions from other reviews. 💯
However, I made some changes like adding links, formatting or rephrasing.

Please review my suggested changes, thx!

[markus2330]

Looks good to me, needs a rebase though.

[kodebach]

Also: Merging this will (probably) cause conflicts in #4187. So I would suggest merging #4187 first and then rebasing this.

[markus2330]

@flo91 can you please rebase, I would like to merge it soon. In the meeting notes there is a link to the documentation guides and it would be great if most people can already read with the fixes.

[flo91]

Thank you for the reminder! 🔔
I almost forgot about this PR. ^^'

I've rebased with current master and added the broken links to the MinGW builds to the linkchecker whitelist. (see issue #4624)

Unfortunately, there seems to be a problem with the javadoc generation on Debian unstable, all three jobs on Debian unstable failed with the same error.
See: https://build.libelektra.org/blue/organizations/jenkins/libelektra/detail/PR-4506/7/pipeline/1093

[markus2330]

Thank you for updating! 🚀

Did you confirm that this problem is independent of this PR? (E.g. by creating an PR with only updating release notes.) Can you change that Javadoc generation will be done on Debian stable (like other docu tasks)?

If it is not so easy, could you please create an issue?

[atmaxinger]

@markus2330 the java doc issue is also appearing in the decision PR #4554, so it seems independent from this PR.

[markus2330]

Please rebase after #4635

[markus2330]

Great job, thank you! ❤️