From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] scripts/release: Update links to use release assets instead of wiki links
Date: Sun, 3 Feb 2019 23:23:48 +0100 [thread overview]
Message-ID: <CAJfZ7=nW+1DnK1T0-0eDuzP48L26B2yMUA44VWfsnxMVEd_k4Q@mail.gmail.com> (raw)
In-Reply-To: <20190131134812.20440-1-plautrba@redhat.com>
On Thu, Jan 31, 2019 at 2:48 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>
> - new release files are created in release/$RELEASE_TAG
> - download links refers to new release assets
>
> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
I have created packages for 2.9-rc1 for Arch Linux without any
trouble, using the information from the GitHub release page and the
generated wiki page
(https://github.com/SELinuxProject/selinux/wiki/Releases).
Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
> ---
> scripts/release | 24 ++++++++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/release b/scripts/release
> index ad10d557..07813749 100755
> --- a/scripts/release
> +++ b/scripts/release
> @@ -7,11 +7,12 @@ if [ \! -d $WIKIDIR ]; then
> git clone git@github.com:SELinuxProject/selinux.wiki.git $WIKIDIR
> fi
>
> -DEST=$WIKIDIR/files/releases/$(date '+%Y%m%d')
> +RELEASE_TAG=$(date '+%Y%m%d')
> +DEST=releases/$RELEASE_TAG
> DIRS="libsepol libselinux libsemanage checkpolicy secilc policycoreutils mcstrans restorecond semodule-utils"
> DIRS_NEED_PREFIX="dbus gui python sandbox"
>
> -git tag -a $(date '+%Y%m%d') -m "Release $(date '+%Y%m%d')"
> +git tag -a $RELEASE_TAG -m "Release $RELEASE_TAG"
>
> rm -rf $DEST
> mkdir -p $DEST
> @@ -44,19 +45,34 @@ echo ""
>
> echo "## Release $(date '+%Y-%m-%d')"
>
> +echo ""
> +
> +echo "[Release Notes](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/RELEASE-$RELEASE_TAG.txt)"
> +echo ""
> +echo "[full log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/log-$RELEASE_TAG.txt)"
> +echo ""
> +echo "[short log](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/shortlog-$RELEASE_TAG.txt)"
> +echo ""
> +
> for i in *.tar.gz; do
>
> - echo -n "[$i](https://raw.githubusercontent.com/wiki/SELinuxProject/selinux/files/releases/$(date '+%Y%m%d')/$i) "
> + echo -n "[$i](https://github.com/SELinuxProject/selinux/releases/download/$RELEASE_TAG/$i) "
> sha256sum $i | cut -d " " -f 1
> echo ""
> done
>
> echo "And then run:"
> echo " cd $WIKIDIR"
> -echo " git commit -m \"Release $(date '+%Y%m%d')\" -a -s"
> +echo " git commit -m \"Release $RELEASE_TAG\" -a -s"
> echo " git push"
>
> echo ""
> echo "Push the release and its tags to git via:"
> echo " git push"
> echo " git push --tags"
> +
> +echo ""
> +echo "Create a new release from the latest tag on https://github.com/SELinuxProject/selinux/tags"
> +
> +echo ""
> +echo "Add files from releases/$RELEASE_TAG as assets to the new github release"
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-03 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:48 [PATCH] scripts/release: Update links to use release assets instead of wiki links Petr Lautrbach
2019-02-03 22:23 ` Nicolas Iooss [this message]
2019-02-06 8:05 ` 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='CAJfZ7=nW+1DnK1T0-0eDuzP48L26B2yMUA44VWfsnxMVEd_k4Q@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=plautrba@redhat.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).