From 3d6fe8e3d9816b0017b9e1d69ced4103f67e7059 Mon Sep 17 00:00:00 2001 From: Tammie Lister Date: Mon, 15 Apr 2019 16:39:15 +0100 Subject: [PATCH] Added point of contact for RC call for testing To ensure every RC has a call for testing, adding myself as a point of contact. Once habit forms here we can remove me. --- docs/contributors/release.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/contributors/release.md b/docs/contributors/release.md index d88c260a3904a9..bfbc84636b3a50 100644 --- a/docs/contributors/release.md +++ b/docs/contributors/release.md @@ -14,7 +14,6 @@ We release a new major version approximately every two weeks. The current and ne On the date of the current milestone, we publish a release candidate and make it available for plugin authors and users to test. If any regressions are found with a release candidate, a new release candidate can be published. - The date in the milestone is the date of **tagging the release candidate**. On this date, all remaining PRs on the milestone are moved automatically to the next release. Release candidates should be versioned incrementally, starting with `-rc.1`, then `-rc.2`, and so on. @@ -74,7 +73,7 @@ Here's an example [release candidate page](https://github.com/WordPress/gutenber ##### Publishing the Call For Testing -Ping someone from the `[#core-test](https://wordpress.slack.com/messages/C03B0H5J0)` team to publish a call for testing post. Here's an [example call for testing post.](https://make.wordpress.org/test/2019/01/04/call-for-testing-gutenberg-4-8/) +Ping @karmatosed in the `[#core-test](https://wordpress.slack.com/messages/C03B0H5J0)` team to publish a call for testing post. Here's an [example call for testing post.](https://make.wordpress.org/test/2019/01/04/call-for-testing-gutenberg-4-8/) #### Creating Release Candidate Patches (done via `git cherry-pick`)