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 version 2.1.0 #79

Closed
10 of 15 tasks
jeffpaul opened this issue Nov 6, 2020 · 0 comments
Closed
10 of 15 tasks

Release version 2.1.0 #79

jeffpaul opened this issue Nov 6, 2020 · 0 comments
Assignees
Milestone

Comments

@jeffpaul
Copy link
Member

jeffpaul commented Nov 6, 2020

This issue is for tracking changes for the 2.1.0 release. Target release date: TBD.

Pre-release steps

Release steps

  • Branch: Starting from develop, cut a release branch named release/2.1.0 for your changes.
  • Version bump: Bump the version number in src/bootstrap.php if it does not already reflect the version being released.
  • Changelog: Add/update the changelog in CHANGELOG.md.
  • Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate
  • Readme updates: Make any other readme changes as necessary in README.md.
  • Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into master (git checkout master && git merge --no-ff develop). master contains the stable development version.
  • Push: Push your trunk branch to GitHub (e.g. git push origin master).
  • Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
  • Check the build: Check out the master branch and test for functionality locally.
  • Release: Create a new release, naming the tag and the release with the new version number, and targeting the master branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases.
  • Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
  • Punt incomplete items: If any open issues or PRs which were milestoned for 2.1.0 do not make it into the release, update their milestone to 2.2.0 or Future Release.
@jeffpaul jeffpaul added this to the 2.1.0 milestone Nov 6, 2020
@jeffpaul jeffpaul self-assigned this Nov 6, 2020
@jeffpaul jeffpaul mentioned this issue Nov 6, 2020
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants