Merge pull request #4244 from pdecat/patch-1

Update the location of the list of staging repositories published

1 files changed, 8 insertions, 19 deletions

diff --git a/contributors/devel/sig-architecture/staging.md b/contributors/devel/sig-architecture/staging.md
index 79ae762f..b255f0fc 100644
--- a/contributors/devel/sig-architecture/staging.md
+++ b/contributors/devel/sig-architecture/staging.md
@@ -4,31 +4,20 @@ The [staging/ directory](https://git.k8s.io/kubernetes/staging) of Kubernetes co
 
 We publish the staging repos using the [publishing bot](https://git.k8s.io/publishing-bot). It uses `git filter-branch` essentially to [cut the staging directories into separate git trees](https://de.slideshare.net/sttts/cutting-the-kubernetes-monorepo-in-pieces-never-learnt-more-about-git) and pushing the new commits to the corresponding real repositories in the [kubernetes organization on Github](https://github.com/kubernetes).
 
-The list of staging repositories and their published branches are listed in [publisher.go inside of the bot](https://git.k8s.io/publishing-bot/cmd/publishing-bot/publisher.go). Though it is planned to move this out into the k8s.io/kubernetes repository.
+The list of staging repositories currently published is available in [staging/README.md inside of the k8s.io/kubernetes repository](https://git.k8s.io/kubernetes/staging/README.md).
 
-At the time of this writing, this includes the branches
+At the time of this writing, the list of published branches includes:
 
 - master,
-- release-1.8 / release-5.0,
-- and release-1.9 / release-6.0
-
-of the following staging repos in the k8s.io org:
-
-- api
-- apiextensions-apiserver
-- apimachinery
-- apiserver
-- client-go
-- code-generator
-- kube-aggregator
-- metrics
-- sample-apiserver
-- sample-controller
+- release-1.14 / release-11.0,
+- release-1.15 / release-12.0,
+- release-1.16 / release-13.0,
+- and release-1.17 / release-14.0
 
 Kubernetes tags (e.g., v1.9.1-beta1) are also applied automatically to the published repositories, prefixed with kubernetes- (e.g., kubernetes-1.9.1-beta1). The client-go semver tags (on client-go only!) including release-notes are still done manually.
 
 The semver tags are still the (well tested) official releases. The kubernetes-1.x.y tags have limited test coverage (we have some automatic tests in place in the bot), but can be used by early adopters of client-go and the other libraries. Moreover, they help to vendor the correct version of k8s.io/api and k8s.io/apimachinery.
 
-If further repos under staging are need, adding them to the bot is easy. Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS).
+If further repos under staging are needed, adding them to the bot is easy. Contact one of the [owners of the bot](https://git.k8s.io/publishing-bot/OWNERS).
 
-Currently, the bot is hosted on the CI cluster of Redhat's OpenShift (ready to be moved out to a public CNCF cluster if we have that in the future).
+Currently, the bot is hosted on a [public CNCF cluster](http://git.k8s.io/publishing-bot/k8s-publishing-bot.md).