From 0ebcc778e33f8caefe4e5768ab522de0d361d992 Mon Sep 17 00:00:00 2001 From: Tim Pepper Date: Mon, 20 Aug 2018 21:35:59 -0700 Subject: contrib guide: update link The SIG-Release ephemera on issue workflow is moved to the devel guide. Updating reference to it. Signed-off-by: Tim Pepper --- contributors/guide/pull-requests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md index cc9f07de..673901ed 100644 --- a/contributors/guide/pull-requests.md +++ b/contributors/guide/pull-requests.md @@ -108,7 +108,7 @@ The GitHub robots will add and remove the `do-not-merge/hold` label as you use t ## Pull Requests and the Release Cycle -If a pull request has been reviewed, but held or not approved, it might be due to the current phase in the [Release Cycle](https://git.k8s.io/sig-release/ephemera). Occasionally, a SIG may freeze their own code base when working towards a specific feature or goal that could impact other development. During this time, your pull request could remain unmerged while their release work is completed. +If a pull request has been reviewed, but held or not approved, it might be due to the current phase in the [Release Cycle](/contributors/devel/release.md). Occasionally, a SIG may freeze their own code base when working towards a specific feature or goal that could impact other development. During this time, your pull request could remain unmerged while their release work is completed. If you feel your pull request is in this state, contact the appropriate [SIG](https://git.k8s.io/community/sig-list.md) or [SIG-Release](https://git.k8s.io/sig-release) for clarification. -- cgit v1.2.3