From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
Richard Palethorpe <rpalethorpe@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/5] Release scripts and docs
Date: Fri, 22 Sep 2023 18:13:04 +0200 [thread overview]
Message-ID: <20230922161304.GA587441@pevik> (raw)
In-Reply-To: <CAASaF6xMijTern9QA4B3zT93kDaZdxK_JMa=+bVMctOtdG5m7g@mail.gmail.com>
Hi Jan, Li,
> On Thu, Sep 21, 2023 at 10:18 AM Li Wang <liwang@redhat.com> wrote:
> > Hi Petr, All,
> > Thanks for writing down the release procedure, very useful.
> +1 for having documented steps
> > But I doubt that we really need the scripts to do release work
> > automatically since we _only_ do the release every four months.
> > It seems to bring additional maintenance work unnecessarily.
> > I personally think the manual step is detailed enough for us.
> > But anyway, now you have done the automation, I don't have
> > an objection to your patch set, just feel that we automate for the
> > sake of automation :).
> > I'd like to hear more opinions, but if most of us think the script is
> > necessary, I'm happy to accept them as well.
> As someone who hasn't done release before, I'd probably do it
> manually first-time to double-check each step.
> It's probably not necessary, but people who did releases many times may
> find it useful - I'm assuming the release procedure isn't changing
> that frequently.
Thanks both for your input.
Yes. Manual process is error prone.
Because I did tagging and tarball generating for last few releases I wanted to
avoid re-reading the documentation during each release and speedup the whole
process. Because there is a lot of "manual" clicking even without it.
BTW the changelog skeleton should be separated to be useful (Cyril does it).
Kind regards,
Petr
> > On Wed, Sep 20, 2023 at 5:53 PM Petr Vorel <pvorel@suse.cz> wrote:
> >> Hi,
> >> copy pasting release is error prone, thus I wrote release scripts.
> >> Any change you would have look on it before release?
> >> 2 commits were already posted before, Li had some notes about the
> >> procedure, thus I updated it.
> >> Kind regards,
> >> Petr
> >> Petr Vorel (5):
> >> tools: Add a script for tagging the release
> >> tools: Add script for creating tarballs and metadata
> >> doc: Rename files to names from ltp.wiki.git
> >> doc: Add Release procedure
> >> doc: Update release procedure
> >> .github/workflows/wiki-mirror.yml | 16 +--
> >> ...ild-system-guide.txt => Build-System.rest} | 0
> >> doc/{c-test-api.txt => C-Test-API.asciidoc} | 0
> >> ...mple.txt => C-Test-Case-Tutorial.asciidoc} | 0
> >> ...-c-api.txt => C-Test-Network-API.asciidoc} | 0
> >> ...kvm-test-api.txt => KVM-Test-API.asciidoc} | 0
> >> ...P-Library-API-Writing-Guidelines.asciidoc} | 0
> >> doc/LTP-Release-Procedure.asciidoc | 116 ++++++++++++++++++
> >> ...aintainer-Patch-Review-Checklist.asciidoc} | 0
> >> ...l-test-api.txt => Shell-Test-API.asciidoc} | 0
> >> ...kernel,-libc,-toolchain-versions.asciidoc} | 0
> >> ...s.txt => Test-Writing-Guidelines.asciidoc} | 0
> >> ...ser-guide.txt => User-Guidelines.asciidoc} | 0
> >> tools/create-tarballs-metadata.sh | 52 ++++++++
> >> tools/lib.sh | 31 +++++
> >> tools/tag-release.sh | 80 ++++++++++++
> >> 16 files changed, 282 insertions(+), 13 deletions(-)
> >> rename doc/{build-system-guide.txt => Build-System.rest} (100%)
> >> rename doc/{c-test-api.txt => C-Test-API.asciidoc} (100%)
> >> rename doc/{c-test-tutorial-simple.txt => C-Test-Case-Tutorial.asciidoc} (100%)
> >> rename doc/{network-c-api.txt => C-Test-Network-API.asciidoc} (100%)
> >> rename doc/{kvm-test-api.txt => KVM-Test-API.asciidoc} (100%)
> >> rename doc/{library-api-writing-guidelines.txt => LTP-Library-API-Writing-Guidelines.asciidoc} (100%)
> >> create mode 100644 doc/LTP-Release-Procedure.asciidoc
> >> rename doc/{maintainer-patch-review-checklist.txt => Maintainer-Patch-Review-Checklist.asciidoc} (100%)
> >> rename doc/{shell-test-api.txt => Shell-Test-API.asciidoc} (100%)
> >> rename doc/{supported-kernel-libc-versions.txt => Supported-kernel,-libc,-toolchain-versions.asciidoc} (100%)
> >> rename doc/{test-writing-guidelines.txt => Test-Writing-Guidelines.asciidoc} (100%)
> >> rename doc/{user-guide.txt => User-Guidelines.asciidoc} (100%)
> >> create mode 100755 tools/create-tarballs-metadata.sh
> >> create mode 100755 tools/lib.sh
> >> create mode 100755 tools/tag-release.sh
> >> --
> >> 2.40.1
> > --
> > Regards,
> > Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-09-22 16:13 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
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 [this message]
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=20230922161304.GA587441@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@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.