[LTP] [PATCH 5/5] doc: Update release procedure

[Petr Vorel]

> Hi!
> > * Mention release preparation (Li Wang).
> > * Replace skeleton commands with the release scripts.
> > * Update link to the release announcement.

> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> >  doc/LTP-Release-Procedure.asciidoc | 111 +++++++++++++++++++++--------
> >  1 file changed, 80 insertions(+), 31 deletions(-)

> > diff --git a/doc/LTP-Release-Procedure.asciidoc b/doc/LTP-Release-Procedure.asciidoc
> > index cd7682fb8..26d85d1fa 100644
> > --- a/doc/LTP-Release-Procedure.asciidoc
> > +++ b/doc/LTP-Release-Procedure.asciidoc
> > @@ -5,54 +5,103 @@ This page contains quick summary of what needs to be done to do a LTP release. I

> >  NOTE: The string YYYYMMDD should be substituted to the current date.

> > -1. Tag the git
> > +1. Release eve work
>                ^
> 	       ?

"Eve" was suggested by Li. While it's a valid word, "preparation" would be
probably better.

> > +-------------------


> > +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

> To be honest this list looks too sparse to be really useful, what about
> a paragraph with more detailed explanations:

> The release procedure generally takes a few weeks. In the first week or
> two patches that should go into the release are reviewed and possibly
> merged. These patches are either fixes or patches pointed out by the
> community. Patch review, when finished, is followed by a git freeze,
> which is a period where only fixes are pushed to the git. During that
> period community is expected to run a LTP pre-release tests, reports
> problems, and/or send fixes to the mailing list. In this period we are
> especially making sure that there are no regressions in the test results
> on a wide range of distributions and architectures. Once the
> stabilization period has ended the time has finally come to proceed with
> the release.

Yes, that looks much better to me.

> > +2. Tag the git
> > --------------------------
> > -[source,sh]
> > ---------------------------------------------------------------------
> > -git push
> > -git push --tags
> > +LTP 20230516

> Do we want to have the XXXXYYZZ here instead?
Sure, I'll replace it with YYYYMMDD.  I started with a real life example, but
then I removed myself...

> > +-----BEGIN PGP SIGNATURE-----
> > +
> > +iQJDBAABCAAtFiEEIBb+pIWLHDazLoM6wN7C7nLzOl8FAmRjD8sPHHB2b3JlbEBz
> > +...
> > +-----END PGP SIGNATURE-----
> > +
> > +commit 3ebc2dfa85c2445bb68d8c0d66e33c4da1e1b3a7
> > +gpg: Signature made Tue 16 May 2023 07:08:08 AM CEST
> > +gpg:                using RSA key 2016FEA4858B1C36B32E833AC0DEC2EE72F33A5F
> > +...
> > +Primary key fingerprint: 2016 FEA4 858B 1C36 B32E  833A C0DE C2EE 72F3 3A5F
> > +Author: Person-who-released LTP <foo@example.com>
> > +Date:   Tue May 16 07:08:08 2023 +0200
> > +
> > +    LTP 20230516

> And here?

> > +    Signed-off-by: Person-who-released LTP <foo@example.com>
> > +
> > +diff --git a/VERSION b/VERSION
> > +index af4c41fec..ae488c0e7 100644
> > +--- a/VERSION
> > ++++ b/VERSION
> > +@@ -1 +1 @@
> > +-20230127
> > ++20230516

> And here?


...
> >  The announcement is send to:

> >  * lwn at lwn.net
> >  * akpm at linux-foundation.org
> > -* torvalds at linux-foundation.org.
Are these mails complete? I would at least add automated-testing@lists.yoctoproject.org.