From 0da3b69b504a8d695af608dcb5ee8e1960d28cc0 Mon Sep 17 00:00:00 2001 From: Fabio Baltieri Date: Mon, 3 Oct 2022 13:57:15 +0000 Subject: [PATCH] doc: release process: stop creating zephyr- prefixed tags Drop the process step to create zephyr- prefixed tags. This has been done so that autogenerated release files have a sensible name, but GitHub started to automatically prefix the project names to release artifacts anyway using HTTP headers, which now results in file named like: zephyr-zephyr-v3.2.0.tar.gz, so the extra tags are now causing the opposite problem. Signed-off-by: Fabio Baltieri --- doc/project/release_process.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/doc/project/release_process.rst b/doc/project/release_process.rst index 7c3ed53982..1e7616bceb 100644 --- a/doc/project/release_process.rst +++ b/doc/project/release_process.rst @@ -420,14 +420,8 @@ steps: $ git tag -s -m "Zephyr 1.11.0" v1.11.0 $ git push git@github.com:zephyrproject-rtos/zephyr.git v1.11.0 - # This is the tag that will represent the release on GitHub, so that - # the file you can download is named ``zephyr-v1.11.0.zip`` and not - # just ``v1.11.0.zip`` - $ git tag -s -m "Zephyr 1.11.0" zephyr-v1.11.0 - $ git push git@github.com:zephyrproject-rtos/zephyr.git zephyr-v1.11.0 - - #. Find the new ``zephyr-v1.11.0`` tag at the top of the releases page - and edit the release with the ``Edit tag`` button with the following: + #. Find the new ``v1.11.0`` tag at the top of the releases page and + edit the release with the ``Edit tag`` button with the following: * Name it ``Zephyr 1.11.0`` * Copy the overview of ``docs/releases/release-notes-1.11.rst`` @@ -449,8 +443,8 @@ cycle you can do the following: #. Look for the last release before the current one and find the day it was tagged:: - $ git show -s --format=%ci zephyr-v1.10.0 - tag zephyr-v1.10.0 + $ git show -s --format=%ci v1.10.0 + tag v1.10.0 Tagger: Kumar Gala Zephyr 1.10.0