From 25a0e7a06740cdf5352aedff6d04090fcf1b0905 Mon Sep 17 00:00:00 2001 From: Daniel Bachhuber Date: Mon, 2 Apr 2018 21:13:22 -0700 Subject: [PATCH] Repository Management: PRs should be milestoned to the release they landed in (#5887) --- docs/repository-management.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/repository-management.md b/docs/repository-management.md index caf6ced90c4cb..d1787e868a4f9 100644 --- a/docs/repository-management.md +++ b/docs/repository-management.md @@ -115,6 +115,8 @@ A pull request can generally be merged once it is: The final pull request merge decision is made by the **@wordpress/gutenberg-core** team. +Please make sure to assign your merged pull request to its release milestone. Doing so creates the historical legacy of what code landed when, and makes it possible for all project contributors (even non-technical ones) to access this information. + ### Closing Pull Requests Sometimes, a pull request may not be mergeable, no matter how much additional effort is applied to it (e.g. out of scope). In these cases, it’s best to communicate with the contributor graciously while describing why the pull request was closed, this encourages productive future involvement.