From d434c2e9c615c1268cc7d0dd19b201877dcb637c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 12 Apr 2021 11:18:59 +0200 Subject: [PATCH 1/3] docs: OBS account is not require anymore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Since we stopped building kata-containers packages as part of our release process, there's no need to have an OBS account to be able to do the release. Fixes: #1680 Signed-off-by: Fabiano Fidêncio --- docs/Release-Process.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index 7be9333900..e11e6dd2d3 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -19,8 +19,6 @@ - [hub](https://github.com/github/hub) -- OBS account with permissions on [`/home:katacontainers`](https://build.opensuse.org/project/subprojects/home:katacontainers) - - GitHub permissions to push tags and create releases in Kata repositories. - GPG configured to sign git tags. https://help.github.com/articles/generating-a-new-gpg-key/ From 8a47b05a7cd578bfa721c82dbb4ec0f67f38c8a9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 12 Apr 2021 11:21:39 +0200 Subject: [PATCH 2/3] docs: Mention that an app token should be used with hub MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit During the 2.1.0-alpha2 / 2.0.3 release, I had a hard time trying to perform anything related to hub as the app token should be used instead of the user password. Thankfully Carlos pointed me out to that direction, but it'd be good to have it explicitly documented. Fixes: #1680 Signed-off-by: Fabiano Fidêncio --- docs/Release-Process.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index e11e6dd2d3..a26152f078 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -18,6 +18,7 @@ ## Requirements - [hub](https://github.com/github/hub) + * Using an [application token](https://github.com/settings/tokens) is required for hub. - GitHub permissions to push tags and create releases in Kata repositories. From 8bc53498b41949514fd00771cd522edbb4f4ed69 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Mon, 12 Apr 2021 11:39:25 +0200 Subject: [PATCH 3/3] docs: Simplify the repo bumping section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Instead of giving too many options, let's just mention the script and rely on it entirely for the release. This helps to simplify the document and have one well stablished process. Fixes: #1680 Signed-off-by: Fabiano Fidêncio --- docs/Release-Process.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index a26152f078..394d235819 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -31,14 +31,9 @@ ### Bump all Kata repositories - - We have set up a Jenkins job to bump the version in the `VERSION` file in all Kata repositories. Go to the [Jenkins bump-job page](http://jenkins.katacontainers.io/job/release/build) to trigger a new job. - - Start a new job with variables for the job passed as: - - `BRANCH=` - - `NEW_VERSION=` - - For example, in the case where you want to make a patch release `1.10.2`, the variable `NEW_VERSION` should be `1.10.2` and `BRANCH` should point to `stable-1.10`. In case of an alpha or release candidate release, `BRANCH` should point to `master` branch. - - Alternatively, you can also bump the repositories using a script in the Kata packaging repo + Bump the repositories using a script in the Kata packaging repo, where: + - `BRANCH=` + - `NEW_VERSION=` ``` $ cd ${GOPATH}/src/github.com/kata-containers/kata-containers/tools/packaging/release $ export NEW_VERSION=