Skip to content

Release version 1.0.1 #43

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.

Sign up for GitHub

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

Jump to bottom
Merged
helen merged 13 commits into from
Sep 6, 2019
Merged

Release version 1.0.1 #43

helen merged 13 commits into from
Sep 6, 2019

Conversation

@jeffpaul
Copy link
Member

@jeffpaul jeffpaul commented Sep 6, 2019 •
edited by helen
Loading

PR for tracking changes for the 1.0.1 release. Target release date: Monday, August 9th.

Release steps

  • Starting from develop, cut a release branch named release/1.0.1 for your changes.
  • Version bump: Bump the version number in insert-special-characters.php and package.json if it does not already reflect the version being released.
  • Changelog: Add/update the changelog in CHANGELOG.md and readme.txt
  • Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
  • 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. master contains the stable development version.
  • Push: Push your master branch to GitHub, e.g. git push origin master.
  • Git tag: Create a new release as 1.0.1 on the master branch in GitHub.
  • Deploy to WordPress.org: Head to the Actions tab in the repo and wait for the Deploy to WordPress.org workflow to finish if it hasn't already. If it doesn't succeed, figure out why and head back to delete the tag and try again.
  • Edit the 1.0.1 milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close 1.0.1 milestone
  • If any open issues or PRs which were milestoned for 1.0.1 do not make it into the release, update their milestone to 1.1.0 or Future Release

@jeffpaul jeffpaul added this to the 1.0.1 milestone Sep 6, 2019
@jeffpaul jeffpaul self-assigned this Sep 6, 2019
@jeffpaul
Copy link
Member Author

jeffpaul commented Sep 6, 2019

Last couple of commits related to #38, but leaving addition of more screenshots for another day.

@jeffpaul jeffpaul added the needs:documentation This requires documentation. label Sep 6, 2019
@jeffpaul jeffpaul marked this pull request as ready for review September 6, 2019 17:19
@jeffpaul
Copy link
Member Author

jeffpaul commented Sep 6, 2019

Ideally #41 and #44 are reviewed/merged ahead of starting this release process. If not, changes to changelog.md and readme.txt will be needed to remove either/both of those PR changelog details.

@jeffpaul jeffpaul mentioned this pull request Sep 6, 2019
Closed
3 tasks
helen
helen previously approved these changes Sep 6, 2019
View reviewed changes
Copy link
Contributor

@helen helen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few suggestions I’m going to merge in and then I think we’re good to go.

@helen helen removed the request for review from adamsilverstein September 6, 2019 22:24
@helen helen merged commit 2f1d2dd into develop Sep 6, 2019
@helen helen deleted the release/1.0.1 branch September 6, 2019 22:29
@jeffpaul jeffpaul mentioned this pull request Sep 9, 2019
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@helen helen helen approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@jeffpaul jeffpaul

Labels

needs:documentation This requires documentation.

Projects

None yet

Milestone

1.0.1

Development

Successfully merging this pull request may close these issues.

2 participants

@jeffpaul @helen