Release 0.5 preparation

[Vezzra]

This issue is used to organize the version 0.5 release of FreeOrion.

Milestones

Important milestones for the release. Changes will be announced by the release
manager.

Date	Milestone
2022-11-13	Create release branch from master
2023-02-16	Release Candidate 1
2023-03-07	Release Candidate 2
2023-03-21	Release Candidate 3
2023-04-02	Declaring Release

Checklist

This is a checklist for the release manager to ensure all steps are done before
doing the actual release.

Preparations

• Create a new GitHub Issue from .github/RELEASE_TEMPLATE.md and follow
  instructions.
• Determine initial milestones and dates for release.
• Update packaging/org.freeorion.FreeOrion.metainfo.xml and linked screenshots if necessary
• Merge PR more gradual and less effective BLD_LIGHTHOUSE effect for planets/buildings #3977 into master
• Create release branch from development branch master by using:

git checkout -b release-v0.5 master

• On release branch HEAD - Update version number in CMakeLists.txt and
  cmake/make_versioncpp.py to v0.5, remove trailing + if needed.
• On release branch HEAD - Disable Super Testers species by default.
• On master branch HEAD - Update version number in CMakeLists.txt and
  cmake/make_versioncpp.py to v0.5+.
• Push updated release and master branch to GitHub.
• Update ChangeLog.md.

Release candidate 1

• Integrate incoming bugfixes.
• Update ChangeLog.md again if needed.
• On release branch HEAD - Tag the release candidate by using:

git tag --annotate --message="0.5 Release Candidate 1"  v0.5-rc1

• Push release candidate tag to GitHub.
• Build release candidate artifacts.
• Upload release candidate artifacts to SourceForge.
• If this is the first release candidate, announce availability of
  release candidates in News section of FreeOrion Wiki.
• Announce release candidate on Twitter as @freeorion
• Test release candidate.

Release candidate 2

• Integrate incoming bugfixes.
• Update ChangeLog.md again if needed.
• On release branch HEAD - Tag the release candidate by using:

git tag --annotate --message="0.5 Release Candidate 2"  v0.5-rc2

• Push release candidate tag to GitHub.
• Build release candidate artifacts.
• Upload release candidate artifacts to SourceForge.
• Announce release candidate on Twitter as @freeorion
• Test release candidate.

Release candidate 3

• Integrate incoming bugfixes.
• Update ChangeLog.md again if needed.
• On release branch HEAD - Tag the release candidate by using:

git tag --annotate --message="0.5 Release Candidate 3"  v0.5-rc3

• Push release candidate tag to GitHub.
• Build release candidate artifacts.
• Upload release candidate artifacts to SourceForge.
• Announce release candidate on Twitter as @freeorion
• Test release candidate.

Declare release

• Determine if another release candidate is needed or if the latest release
  candidate is ready to be declared as the official stable release.
• On release branch - Tag the release from the latest release candidate
  by using:

git tag --annotate --message="0.5 Stable Release"  v0.5

• Push release tag to GitHub.
• Write Key Changes description for GitHub releases page.
• Upload release artifacts to GitHub.
• Announce release in News section of FreeOrion Wiki.
• Update Main page of FreeOrion Wiki.
• Update Download page of FreeOrion Wiki.
• Announce release on Twitter as @freeorion
• Announce release on YouTube.

Cleanup

• Cherry-pick updates of ChangeLog.md to master.
• Prune release candidate tags.
• Prune release branch.

Blocking issues and PRs

Issues and PRs blocking v0.5

[o01eg]

To not forget also merge #4295 to release branch after split.

[Vezzra]

Ok. I can't change your PR to be set against the release branch instead of master (or at least I don't know how to do that), so I will simply take your revert-species-parser branch and merge that directly via git into the release branch.

[o01eg]

@Vezzra I can edit PR and choose other branch.

[Vezzra]

Ok, I'll notify you after the release branch has been created, then you can do it yourself.