From 10ed3da4ebe2b8b4df280f50b0df3578ce30d5fd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Tue, 23 Feb 2021 17:23:55 +0100 Subject: [PATCH] release: Rename runtime-release-notes to release-notes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There's no runtime repo anymore, let's avoid making a reference to it, which may end up confusing people reading the Release-Process file. Signed-off-by: Fabiano FidĂȘncio --- docs/Release-Process.md | 4 ++-- .../release/{runtime-release-notes.sh => release-notes.sh} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename tools/packaging/release/{runtime-release-notes.sh => release-notes.sh} (100%) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index 86085c251..7be933390 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -79,9 +79,9 @@ ``` $ cd ${GOPATH}/src/github.com/kata-containers/kata-containers/tools/packaging/release # Note: OLD_VERSION is where the script should start to get changes. - $ ./runtime-release-notes.sh ${OLD_VERSION} ${NEW_VERSION} > notes.md + $ ./release-notes.sh ${OLD_VERSION} ${NEW_VERSION} > notes.md # Edit the `notes.md` file to review and make any changes to the release notes. - # Add the release notes in GitHub runtime. + # Add the release notes in the project's GitHub. $ hub release edit -F notes.md "${NEW_VERSION}" ``` diff --git a/tools/packaging/release/runtime-release-notes.sh b/tools/packaging/release/release-notes.sh similarity index 100% rename from tools/packaging/release/runtime-release-notes.sh rename to tools/packaging/release/release-notes.sh