From 317f69a964be1c3cb30828e5688b14fda1747c4f Mon Sep 17 00:00:00 2001 From: Thomas Stromberg Date: Fri, 5 Oct 2018 14:53:50 -0700 Subject: [PATCH] Split releases.json work, since it cannot be done until after the Jenkins workflow --- docs/contributors/releasing_minikube.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/contributors/releasing_minikube.md b/docs/contributors/releasing_minikube.md index c7c88165b..182aa7ba0 100644 --- a/docs/contributors/releasing_minikube.md +++ b/docs/contributors/releasing_minikube.md @@ -39,9 +39,7 @@ This will update users of HEAD to the new ISO. Please pay attention to test failures, as this is our integration test across platforms. If there are known acceptable failures, please add a PR comment linking to the appropriate issue. -## Update Release Notes and `releases.json` - -Add the checksums for the release to the top of `deploy/minikube/releases.json`. This file is used for auto-update notifications. The notifications are not activated until this file is copied to GCS. +## Update Release Notes Then run the following script to update the release notes: @@ -73,6 +71,10 @@ Create a new release based on your tag, like [this one](https://github.com/kuber Upload the files, and calculated checksums. +## Update releases.json + +Send out a PR to update the release checksums at the top of `deploy/minikube/releases.json`. This file is used for auto-update notifications, but is not active until releases.json is copied to GCS. + ## Upload releases.json to GCS This step makes the new release trigger update notifications in old versions of Minikube. -- GitLab