summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Arver <linusa@google.com>2019-02-12 15:01:48 -0800
committerLinus Arver <linusa@google.com>2019-02-12 16:07:34 -0800
commitcd82abf431b02754ef56483eddb26af556481af2 (patch)
tree801e4bc1eb9e3024d5516d7793e901563a3b3355
parent243d61ce4b3341cfdeddb8dcbd5d63103d099df1 (diff)
Add explicit links to release-engineering in sig-release
It's confusing having two links for the release-engineering subproject without any description of each. The k/release repo houses all of the existing tooling, such as anago, while the k/sig-release repo houses the procedures and processes. Add these links explicitly to the description so that newcomers have a clearer idea of where to get started.
-rw-r--r--sig-release/README.md2
-rw-r--r--sigs.yaml6
2 files changed, 5 insertions, 3 deletions
diff --git a/sig-release/README.md b/sig-release/README.md
index d0ecca7e..630ed0d6 100644
--- a/sig-release/README.md
+++ b/sig-release/README.md
@@ -47,7 +47,7 @@ The following subprojects are owned by sig-release:
- Owners:
- https://raw.githubusercontent.com/kubernetes/sig-release/master/licensing/OWNERS
- **release-engineering**
- - Description: The Release Engineering subproject is responsible for the process/procedures/tools used to create/maintain Kubernetes release artifacts.
+ - Description: The Release Engineering subproject is responsible for the [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering) and [tools](https://github.com/kubernetes/release) used to create/maintain Kubernetes release artifacts.
- Owners:
- https://raw.githubusercontent.com/kubernetes/release/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/sig-release/master/release-engineering/OWNERS
diff --git a/sigs.yaml b/sigs.yaml
index 08400819..b35ed821 100644
--- a/sigs.yaml
+++ b/sigs.yaml
@@ -1586,8 +1586,10 @@ sigs:
- https://raw.githubusercontent.com/kubernetes/sig-release/master/licensing/OWNERS
- name: release-engineering
description: >
- The Release Engineering subproject is responsible for the process/procedures/tools
- used to create/maintain Kubernetes release artifacts.
+ The Release Engineering subproject is responsible for the
+ [process/procedures](https://github.com/kubernetes/sig-release/tree/master/release-engineering)
+ and [tools](https://github.com/kubernetes/release) used to
+ create/maintain Kubernetes release artifacts.
owners:
- https://raw.githubusercontent.com/kubernetes/release/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/sig-release/master/release-engineering/OWNERS