Re: [LTP] [RFC PATCH 2/2] doc: Add Release procedure

[Petr Vorel <pvorel@suse.cz>]

Hi Li,

> > +++ b/doc/LTP-Release-Procedure.asciidoc
> > @@ -0,0 +1,67 @@
> > +LTP Release Procedure
> > +=====================
> > +
> > +This page contains quick summary of what needs to be done to do a LTP release. It's expected that LTP git is frozen and git HEAD was properly tested and that LTP git tree is cloned to a directory named 'ltp'.

> Should we mention the release is happening every 4 months?

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

> Or, maybe add one more item about the release eve work?
> Like what we discussed in:
>   - https://lists.linux.it/pipermail/ltp/2022-September/030614.html

> For example:

> 0. Release eve work
> ---------------------------

> [source,sh]
> --------------------------------------------------------------------

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

Very good point, I agree with both. Thanks!

Kind regards,
Petr

> > +1. Tag the git
> > +--------------
...

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp