We don't really use the ready-for-review label to signal things anymore

This commit is contained in:
kuychaco 2019-10-17 12:38:37 -07:00
parent f9d7e6227a
commit dea4f25f39

View file

@ -136,7 +136,7 @@ Add your new changelog entries to `changelog.json`, update the version in `app/p
If a maintainer would like to backport a pull request to the next release, it is their responsibilty to co-ordinate with the release owner and ensure they are fine with accepting this work.
Once your release branch is ready to review and ship, add the `ready-for-review` label and ask the other maintainers to review and approve the changes!
Once your release branch is ready to review and ship, ask the other maintainers to review and approve the changes!
IMPORTANT NOTE: Do NOT "Update branch" and merge development into the release branch. This might be tempting if the "branch is out-of-date with the base branch" dotcom feature is enabled. However, doing so would inadvertently release everything on development to production or beta 🙀