summaryrefslogtreecommitdiff
path: root/contributors/guide
diff options
context:
space:
mode:
authoreduartua <eduartua@gmail.com>2019-01-29 11:23:48 -0600
committereduartua <eduartua@gmail.com>2019-01-29 11:23:48 -0600
commitf684fcb8dff1641f11924fb23fcb4732cf4a97c8 (patch)
tree63aa04023584fd9c6a8587da903150a5a9def031 /contributors/guide
parent5a4bdf39dbb198fc161303dcc9b71b855053f08d (diff)
file release.md has been moved to /devel/sig-release - URLs in k/community updated
Diffstat (limited to 'contributors/guide')
-rw-r--r--contributors/guide/issue-triage.md2
-rw-r--r--contributors/guide/pull-requests.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md
index ff67ba3e..879648a9 100644
--- a/contributors/guide/issue-triage.md
+++ b/contributors/guide/issue-triage.md
@@ -206,7 +206,7 @@ block the release on it. A few days before release, we will probably move all
that milestone in bulk.
More information can be found in the developer guide section for
-[targeting issues and PRs to a milestone release](/contributors/devel/release.md).
+[targeting issues and PRs to a milestone release](/contributors/devel/sig-release/release.md).
## Closing issues
Issues that are identified as a support request, duplicate, not-reproducible
diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md
index a24310a6..a9c26086 100644
--- a/contributors/guide/pull-requests.md
+++ b/contributors/guide/pull-requests.md
@@ -115,7 +115,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](/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 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/sig-release/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.