Skip to content

Instantly share code, notes, and snippets.

@grahamc
Last active October 18, 2019 19:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save grahamc/8e2e5e275610d9e07a5549bcc0f15ab5 to your computer and use it in GitHub Desktop.
Save grahamc/8e2e5e275610d9e07a5549bcc0f15ab5 to your computer and use it in GitHub Desktop.
* make sure every PR which needs release notes gets rnlease notes
* bot which can do backports
make teams:
| two is hard enough, six would be harder to get done.
|
| * one or two people responsible for keeping an eye on issues and pull requests
| * role: responsible for backport. especially during freeze.
| * role: architecture position, planning big things to get done for a release.
"working groups" to organize changes.
TODO: a call with people in the community to find out what should be in the next release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment