[x] 1. Branch: Starting from develop, create a new branch following the format release/2.8.4.
[x] 2. Version bump: Update the plugin version in readme.txt, package.json, package-lock.json, brightcove-video-connect.php in plugin version and BRIGHTCOVE_VERSION constant.
[x] 4. New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
[x] 5. If applicable, bump the Tested up to field in readme.txt.
[x] 6. Release date: Double check the release date in both changelog files.
[x] 7. Run npm run build to generate updated translation files.
[x] 8. Commit your changes and open a PR to develop.
[x] 9. Once changes are merged, open a PR from develop to master.
[x] 10. Test: Once changes are merged, checkout the master branch locally and test for functionality.
[x] 11. Release: Once merged, draft a new release naming the release with the new version number, creating a new label 2.8.4, and selecting as target master. Paste the release changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone.
[x] 12. 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.
[x] 14. 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.
[x] 15. Punt incomplete items: If any open issues or PRs which were milestoned for 2.8.4 do not make it into the release, update their milestone to 2.8.5, 2.9.0, 3.0.0 or Future Release.
develop, create a new branch following the formatrelease/2.8.4.readme.txt,package.json,package-lock.json,brightcove-video-connect.phpin plugin version andBRIGHTCOVE_VERSIONconstant.CHANGELOG.mdandreadme.txt, ensuring to link the [2.8.4] release reference in the footer ofCHANGELOG.md(e.g., https://github.com/10up/brightcove-video-connect/compare/2.8.3...2.8.4)..gitattributes.Tested up tofield inreadme.txt.npm run buildto generate updated translation files.develop.developtomaster.masterbranch locally and test for functionality.2.8.4, and selecting as targetmaster. Paste the release changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone.Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.2.8.4do not make it into the release, update their milestone to2.8.5,2.9.0,3.0.0orFuture Release.