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.

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

Release version 1.1.2 #113

Closed
15 of 16 tasks
jeffpaul opened this issue May 25, 2023 · 1 comment · Fixed by #114
Closed
15 of 16 tasks

Release version 1.1.2 #113

jeffpaul opened this issue May 25, 2023 · 1 comment · Fixed by #114
Assignees
@jeffpaul
Milestone
1.1.2

Comments

@jeffpaul
Copy link
Member

jeffpaul commented May 25, 2023 •
edited

Describe your question

This issue is for tracking changes for the 1.1.1 release. Target release date: May 2023.

Release steps

  • Branch: Starting from develop, cut a release branch named release/1.1.2 for your changes.
  • Version bump: Bump the version number in ad-refresh-control.php, package.json, package-lock.json and readme.txt if it does not already reflect the version being released. In ad-refresh-control.php update both the plugin "Version:" property and the plugin AD_REFRESH_CONTROL_VERSION constant.
  • Changelog: Add/update the changelog in both CHANGELOG.md and readme.txt.
  • Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
  • Readme updates: Make any other readme changes as necessary. README.md is geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different.
  • New files: 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 trunk, ensuring you pull the most recent changes into develop first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
  • Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
  • Compare trunk to develop to ensure no additional changes were missed.
  • Test the pre-release ZIP locally by downloading it from the Build release zip action artifact and installing it locally. Ensure this zip has all the files we expect, that it installs and activates correctly and that all basic functionality is working.
  • Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone (e.g. https://github.com/10up/ad-refresh-control/milestone/10?closed=1).
  • SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
  • Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/ad-refresh-control/. This may take a few minutes.
  • 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 1.1.2 do not make it into the release, update their milestone to 1.2.0 or Future Release.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jeffpaul jeffpaul added this to the 1.2.0 milestone May 25, 2023
@jeffpaul jeffpaul self-assigned this May 25, 2023
@jeffpaul jeffpaul mentioned this issue May 25, 2023
Merged
4 tasks
@jeffpaul
Copy link
Member Author

Seeing a build error in the deploy action: https://github.com/10up/Ad-Refresh-Control/actions/runs/5272088906/jobs/9533888315

@jeffpaul jeffpaul reopened this Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeffpaul jeffpaul

Labels
None yet
Projects
Open Source Practice
Archived in project
Milestone
1.1.2
Development

Successfully merging a pull request may close this issue.

Release/1.1.2 10up/Ad-Refresh-Control
1 participant
@jeffpaul