Release 0.15.0

[kasparsd]

Trying out the updated RELEASE.md process.

Diff: 0.14.2...release/0.15.0

Release instructions

• Branch: Starting from master, create a branch named release/X.Y.Z for the release-related changes.
• Version bump: Bump the version number in readme.txt and two-factor.php if it does not already reflect the version being released. Update both the plugin "Version:" header value and the plugin TWO_FACTOR_VERSION constant in two-factor.php.
• Changelog: Add/update the changelog in CHANGELOG.md. The changelog can be generated from a compare URL like 0.14.2...HEAD. Ensure the version number is added to the footer links at the bottom showing the compare from the prior version (e.g., 0.14.2...0.15.0). Trim the changelog entry in readme.txt to the least recent between a year ago and the prior major release.
• Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate. With the CHANGELOG.md updates completed in the step previous, open those PRs merged in the release, open the merge commits from them, and then assuming the Props Bot recommendations for Co-Authored By are included in the merge commits those GitHub usernames and the person making the merge commit can be added (where missing) to the CREDITS.md file.
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
• 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.
• Create Release PR: Push any local changes in release/X.Y.Z to origin, create a release PR, and request review to ensure all CI checks pass and ensure master branch changes are limited to merges only.
• Test: Test a ZIP built from the Release PR branch to ensure key plugin functionality continues to work and that the Tests action passes on the PR.
• Merge: After review approval, merge the release pull request (or make a non-fast-forward merge from your release branch to master). master contains the latest stable release.
• 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 items on the milestone. Creating a release will automatically generate & attach zip/tarball files, so you can ignore the GitHub release form asking to uploaded those assets.
• SVN: Wait for the GitHub Action: Deploy to finish deploying to the WordPress.org repository.
• Release confirmation: Someone with committer access on WP.org needs to confirm the release at https://wordpress.org/plugins/two-factor/advanced/. 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/two-factor/. This may take a few minutes.
• Close the milestone: Edit the milestone with the release date (in the Due date (optional) field) and link to the GitHub release (in the Description field), then close the milestone.
• Punt incomplete items: If any open issues or PRs which were milestoned for X.Y.Z do not make it into the release, update their milestone to X.Y.Z+1, X.Y+1.0, X+1.0.0 or Future Release.`

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: kasparsd <kasparsd@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[jeffpaul]

Looks good, thanks for handling the release!