New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.4.8 preparation #2111
Comments
As this is purely an "administrative"/"management" issue, basically a checklist for the release procedure, assigning this to a milestone (especially the mandatory milestone, as this issue doesn't block anything), doesn't make much sense. |
Milestones have been updated. |
Milestones have been updated. |
Milestones have been updated. |
1 similar comment
Milestones have been updated. |
RC3 has been released, checklist updated accordingly. |
0.4.8 has been released, checklist items updated accordingly. |
This issue is used to organize the version 0.4.8 release of FreeOrion.
Milestones
Important milestones for the release. Changes will be announced by the release
manager.
July 19th, 1pmRelease Candidate 3June 28th, 1pmDeclaring ReleaseJuly 22nd, 1pmDeclaring ReleaseJuly 23rd, 1pmDeclaring ReleaseAll times are UTC.
Checklist
This is a checklist for the release manager to ensure all steps are done before
doing the actual release.
Preparations
.github/RELEASE_TEMPLATE.md
and followinstructions.
CMakeLists.txt
andcmake/make_versioncpp.py
tov0.4.8
, remove trailing+
if needed.Super Testers
species by default.CMakeLists.txt
andcmake/make_versioncpp.py
tov0.4.8+
.ChangeLog.md
.Release candidate 1
ChangeLog.md
again if needed.News
sectionof FreeOrion Wiki.
Release candidate 2
ChangeLog.md
again if needed.Release candidate 3
ChangeLog.md
again if needed.Declare release
candidate is ready to be declared as the official stable release.
by using:
Key Changes
description for GitHub releases page.News
section of FreeOrion Wiki.Main
page of FreeOrion Wiki.Download
page of FreeOrion Wiki.Cleanup
ChangeLog.md
to master.Blocking issues
Issues and PRs blocking v0.4.8
The text was updated successfully, but these errors were encountered: