Release Procedures

Create a Release Branch

1. First fork master and create a release branch, e.g. release-x.x.x or release-next
2. Do your work there or merge things into that release branch never update master
3. When the release branch is ready, merge it into master (follow below steps) upon proper approval

When you create a release branch, the first thing you should do is bump the versions and start a release PR into master. Then, copy and paste the code below into the details of the release, and do these things:

- [ ] Ensure release is tested in common Editors (and add Labels accordingly)
- [ ] Bump Plugin Versions
- [ ] Update change log in `README.md`
- [ ] Convert any `@since NEXT`
- [ ] Get PR approval from Director of Engineering
- [ ] Merge release PR into `master`
- [ ] Tag release
- [ ] Copy change log deets to release
- [ ] Update on packagist.org
- [ ] Make post/update Slack