From ca393bb8ace682194fd010be6e056dda6d4298f4 Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Tue, 27 Jun 2017 04:13:44 +0530 Subject: Fix minor typos in cherry-picks doc --- contributors/devel/cherry-picks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributors/devel/cherry-picks.md b/contributors/devel/cherry-picks.md index 484fdde3..1a6d621e 100644 --- a/contributors/devel/cherry-picks.md +++ b/contributors/devel/cherry-picks.md @@ -1,12 +1,12 @@ # Overview -This document explains cherry picks are managed on release branches within the +This document explains how cherry picks are managed on release branches within the Kubernetes projects. Patches are either applied in batches or individually depending on the point in the release cycle. ## Propose a Cherry Pick -1. Cherrypicks are [managed with labels and milestones](pull-requests.md#release-notes) +1. Cherrypicks are [managed with labels and milestones](pull-requests.md#write-release-notes-if-needed) 1. To get a PR merged to the release branch, first ensure the following labels are on the original **master** branch PR: * An appropriate milestone (e.g. v1.3) -- cgit v1.2.3