From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Cc: Hu Keping <hukeping@huawei.com>
Subject: [PATCH 2/3] Use X.Y instead of date for release tag
Date: Fri, 27 Nov 2020 09:52:20 +0100 [thread overview]
Message-ID: <20201127085220.813760-3-plautrba@redhat.com> (raw)
In-Reply-To: <20201127085220.813760-1-plautrba@redhat.com>
From: Hu Keping <hukeping@huawei.com>
As per discussed at github issue[1] and mailing list[2], we consider
a version format of X.Y starting at 3.2.
[1]: https://github.com/SELinuxProject/selinux/issues/270
[2]: https://lore.kernel.org/selinux/87d004wan2.fsf@redhat.com/T/#u
Signed-off-by: Hu Keping <hukeping@huawei.com>
---
scripts/release | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/release b/scripts/release
index 0781374954e4..040aaf68e86a 100755
--- a/scripts/release
+++ b/scripts/release
@@ -7,7 +7,7 @@ if [ \! -d $WIKIDIR ]; then
git clone git@github.com:SELinuxProject/selinux.wiki.git $WIKIDIR
fi
-RELEASE_TAG=$(date '+%Y%m%d')
+RELEASE_TAG=`cat VERSION`
DEST=releases/$RELEASE_TAG
DIRS="libsepol libselinux libsemanage checkpolicy secilc policycoreutils mcstrans restorecond semodule-utils"
DIRS_NEED_PREFIX="dbus gui python sandbox"
@@ -43,7 +43,7 @@ echo "Add the following to the $WIKIDIR/Releases.md wiki page:"
echo ""
-echo "## Release $(date '+%Y-%m-%d')"
+echo "## Release $RELEASE_TAG"
echo ""
--
2.29.2
next prev parent reply other threads:[~2020-11-27 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:52 https://github.com/SELinuxProject/selinux/pull/271 Petr Lautrbach
2020-11-27 8:52 ` [PATCH 1/3] Introduce VERSION file for selinux Petr Lautrbach
2020-11-27 8:52 ` Petr Lautrbach [this message]
2020-11-27 8:52 ` [PATCH 3/3] Simplify the tarball generating scripts Petr Lautrbach
2020-11-27 9:36 ` https://github.com/SELinuxProject/selinux/pull/271 Petr Lautrbach
2020-12-02 17:34 ` https://github.com/SELinuxProject/selinux/pull/271 Petr Lautrbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201127085220.813760-3-plautrba@redhat.com \
--to=plautrba@redhat.com \
--cc=hukeping@huawei.com \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).