From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Richard Palethorpe <rpalethorpe@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 5/5] doc: Update release procedure
Date: Mon, 25 Sep 2023 14:50:37 +0200 [thread overview]
Message-ID: <20230925125037.GA60471@pevik> (raw)
In-Reply-To: <CAEemH2du9Or2y84qF8uHWAO8_+jLfvV+1b6iwBkBdd4abUiZ3A@mail.gmail.com>
> On Mon, Sep 25, 2023 at 5:14 AM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Li,
> > > Hi Petr,
> > ...
> > > > -1. Tag the git
> > > > +1. Release eve work
> > > > +-------------------
> > > > +
> > > > +a. Collecting the (must have) patch list for new release
> > > > +b. Reviewing and merging the patch list of (a.)
> > > > +c. Widely testing, explicitly post results
> > > > +d. Tiny fix according to release testing
> > > > +e. Writing release note
> > > > +
> > > > +2. Tag the git
> > > > --------------
> > > > +Use './tools/tag-release.sh' script, which creates the tag and push
> > it to
> > > > github.
> > > > [source,sh]
> > > > --------------------------------------------------------------------
> > > > -cd ltp
> > > > -echo YYYYMMDD > VERSION
> > > > -git commit -s -m 'LTP YYYYMMDD' VERSION
> > > > -git tag -a YYYYMMDD -m 'LTP YYYYMMDD'
> > > > ---------------------------------------------------------------------
> > > What about adding those manual steps into tag-release.sh as code
> > comments?
> > > That'd be helpful to people who never do release work to try that first
> > > time.
> > Good point, makes sense.
> > I suppose you mean to bput them at the top like this:
> Yes, even looks verbose, but will be helpful to people who never do release
> work.
Sure, no problem. I put all commands.
Kind regards,
Petr
> > #!/bin/sh
> > # Copyright (c) 2023 Petr Vorel <pvorel@suse.cz>
> > # Create tarballs and metadata for uploading after tagging release.
> > # https://github.com/linux-test-project/ltp/wiki/LTP-Release-Procedure
> > # echo YYYYMMDD > VERSION
> > # git commit -s -m 'LTP YYYYMMDD' VERSION
> > # git tag -a YYYYMMDD -m 'LTP YYYYMMDD'
> > set -e
> > ...
> > Because there are comments at the top of each "section" (e.g. # git clone
> > (local))
> > ...
> > > > -cd ..
> > > > -git clone ltp ltp-full-YYYYMMDD
> > > > -cd ltp-full-YYYYMMDD
> > > > -# Update mce-inject submodule
> > > > -git submodule init
> > > > -git submodule update
> > > > -# Generate configure script
> > > > -make autotools
> > > > -# Prepare the archives
> > > > -cd ..
> > > > -tar -cjf ltp-full-YYYYMMDD.tar.bz2 ltp-full-YYYYMMDD --exclude .git
> > > > -tar -cJf ltp-full-YYYYMMDD.tar.xz ltp-full-YYYYMMDD --exclude .git
> > > I suggest adding these into create-tarballs-metadata.sh comments as well.
> > # git clone ltp ltp-full-YYYYMMDD && cd -
> > # git submodule update --init
> > # make autotools
> > # cd ..
> > # tar -cjf ltp-full-YYYYMMDD.tar.bz2 ltp-full-YYYYMMDD --exclude .git
> > # tar -cJf ltp-full-YYYYMMDD.tar.xz ltp-full-YYYYMMDD --exclude .git
> > # sha256sum ltp-full-YYYYMMDD.tar.xz > ltp-full-YYYYMMDD.tar.xz.sha256
> > (Adding all checksums would look to me quite verbose (6 lines), but I can
> > add
> > them.)
> > Kind regards,
> > Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-25 12:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:53 [LTP] [PATCH 0/5] Release scripts and docs Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 1/5] tools: Add a script for tagging the release Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 2/5] tools: Add script for creating tarballs and metadata Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 3/5] doc: Rename files to names from ltp.wiki.git Petr Vorel
2023-09-26 11:47 ` Cyril Hrubis
2023-09-20 9:53 ` [LTP] [PATCH 4/5] doc: Add Release procedure Petr Vorel
2023-09-26 11:46 ` Cyril Hrubis
2023-09-26 13:39 ` Petr Vorel
2023-09-20 9:53 ` [LTP] [PATCH 5/5] doc: Update release procedure Petr Vorel
2023-09-20 15:29 ` Petr Vorel
2023-09-20 15:39 ` Petr Vorel
2023-09-24 0:35 ` Li Wang
2023-09-24 21:14 ` Petr Vorel
2023-09-25 2:31 ` Li Wang
2023-09-25 12:50 ` Petr Vorel [this message]
2023-09-27 6:44 ` Petr Vorel
2023-09-26 12:14 ` Cyril Hrubis
2023-09-26 13:54 ` Petr Vorel
2023-09-26 14:23 ` Cyril Hrubis
2023-09-26 15:29 ` Petr Vorel
2023-09-21 8:18 ` [LTP] [PATCH 0/5] Release scripts and docs Li Wang
2023-09-21 8:43 ` Jan Stancek
2023-09-22 16:13 ` Petr Vorel
2023-09-26 12:22 ` Cyril Hrubis
2023-09-26 13:46 ` Petr Vorel
2023-09-26 13:48 ` Cyril Hrubis
2023-09-26 12:16 ` Cyril Hrubis
2023-09-26 13:41 ` Petr Vorel
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=20230925125037.GA60471@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=yangx.jy@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.