Skip to content
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

Closed
Vezzra opened this issue May 18, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@Vezzra
Copy link
Member

commented May 18, 2018

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.

Date Milestone
May 20th 2018, 6pm Create release branch from master
June 14th, 1pm Release Candidate 1
July 13th, 1pm Release Candidate 2
July 19th, 1pm Release Candidate 3
August 23rd 2018, 1pm Release Candidate 3
June 28th, 1pm Declaring Release
July 22nd, 1pm Declaring Release
July 23rd, 1pm Declaring Release
August 30th 2018, 1pm Declaring Release

All times are UTC.

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.
  • Create release branch from development branch master by using:
git checkout -b release-v0.4.8 master
  • On release branch HEAD - Update version number in CMakeLists.txt and
    cmake/make_versioncpp.py to v0.4.8, 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.4.8+.
  • 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.4.8 Release Candidate 1" v0.4.8-rc1
  • Push release candidate tag to GitHub.
  • Build release candidate artifacts.
  • Upload release candidate artifacts to SourceForge.
  • 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.4.8 Release Candidate 2" v0.4.8-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.4.8 Release Candidate 3" v0.4.8-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.4.8 Stable Release" v0.4.8
  • 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

Issues and PRs blocking v0.4.8

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented May 20, 2018

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.

@Vezzra Vezzra removed this from the v0.4.8 (mandatory) milestone May 20, 2018

@adrianbroher adrianbroher modified the milestone: v0.4.8 (mandatory) Jun 7, 2018

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Jul 9, 2018

Milestones have been updated.

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Jul 17, 2018

Milestones have been updated.
Section for RC3 has been added.

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Jul 19, 2018

Milestones have been updated.

1 similar comment
@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Aug 19, 2018

Milestones have been updated.

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Aug 23, 2018

RC3 has been released, checklist updated accordingly.

@Vezzra

This comment has been minimized.

Copy link
Member Author

commented Aug 30, 2018

0.4.8 has been released, checklist items updated accordingly.

@Vezzra Vezzra closed this Aug 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.