public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
	LTP List <ltp@lists.linux.it>,
	Martin Doucha <martin.doucha@suse.com>,
	automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] September LTP release
Date: Mon, 26 Sep 2022 11:58:24 +0200	[thread overview]
Message-ID: <YzF3wLk9cMTdU1z7@yuki> (raw)
In-Reply-To: <CAEemH2eNjP++fxhP5ZSsX+fq5vAd6h0_qNX6Rx82AdpzN9fyGQ@mail.gmail.com>

Hi!
> Well, if more than three people are involved in the release work,
> I think that the release workflow should be arranged in time order,
> otherwise, we're easily going to fall into chaos. e.g.
> 
> Assumption work starting from the second week of the release month:
> 
> 1. Collecting the patch list for a new release, like this email does (Cyril)
> 
> 2. Reviewing and merging the patch list of step1 (All maintainers,
> LTP-users)
> 
> 3. Pre-release widely testing, we need to explicitly post results in step1
> email (Petr, Li Wang)
> 
> 4. Tiny fix according to pre-release testing result (All maintainers, users)
> 
> 5. Writing release note (Cyril)
> 
> 6. Uploading tarballs (Petr)
> 
> 7. Announcement email of LTP release (Cyril)

Lets move on with the plannig, I would say that we are done with step 2.
and we should move to step 3.

Also I would go for a release date at the end of the month that is 30.9.

Does everyone agree?

-- 
Cyril Hrubis
chrubis@suse.cz

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

  parent reply	other threads:[~2022-09-26  9:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  8:49 [LTP] September LTP release Cyril Hrubis
2022-09-09 10:39 ` Li Wang
2022-09-09 11:10   ` Cyril Hrubis
2022-09-09 14:36     ` Petr Vorel
2022-09-13  7:11       ` Li Wang
2022-09-13 11:50         ` Cyril Hrubis
2022-09-26  9:58         ` Cyril Hrubis [this message]
2022-09-26 10:13           ` Li Wang
2022-09-26 12:26             ` Petr Vorel
2022-09-27  7:44             ` Li Wang
2022-09-27  8:10               ` Petr Vorel
2022-09-27  8:25                 ` Li Wang
2022-09-30 14:00                   ` Petr Vorel
2022-09-26 10:43           ` Petr Vorel
2022-09-26 10:48           ` Petr Vorel
2022-09-09 14:56   ` Petr Vorel
2022-09-12  9:36     ` Cyril Hrubis
2022-09-12  9:45       ` Petr Vorel
2022-09-13  8:19 ` xuyang2018.jy
2022-09-13  9:23   ` Cyril Hrubis
2022-09-19 15:31 ` Petr Vorel
2022-09-23 11:01   ` Petr Vorel
2022-09-23 11:59     ` Cyril Hrubis
2022-09-23 12:16       ` Petr Vorel
2022-09-26  9:49         ` Cyril Hrubis
2022-09-30 10:05 ` 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=YzF3wLk9cMTdU1z7@yuki \
    --to=chrubis@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    --cc=rpalethorpe@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox