All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
	Xiao Yang <yangx.jy@cn.fujitsu.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] LTP release preparations
Date: Thu, 11 May 2023 13:48:15 +0800	[thread overview]
Message-ID: <CAEemH2eqtdEjoopsX0gsWgu5z8s6hgcTVAXM85t2n5a4ccYDVg@mail.gmail.com> (raw)
In-Reply-To: <20230510130347.GA225439@pevik>

On Wed, May 10, 2023 at 9:03 PM Petr Vorel <pvorel@suse.cz> wrote:

> Hi Cyril, Li, others,
>
> I see we're still discussing hugemmap test issues with FILE_PRINTF().
> Do we want to solve these before release?
>

I have merged the quick fix with Cryil's ack. So FILE_PRINTF() improvement
work can be delayed after release.



>
> Because if we want to release on Friday, we should start writing release
> notes
> and announcement. We're on a LABS conference next week. But not sure if
> it's a
> good idea to postpone (Cyril is and will be even more busy, I'll be away
> for few
> weeks before the end of the month).
>

IMO, it's OK to release on Friday, new test based on the latest commit
looks good.



>
> From the list we agreed previously [1]:
>
>     - announcement email,
>     - collecting patch lists for a new release,
>     - writing release notes, or paperwork,
>         - new release commit and tag and create release in github from it
> (not in [1], but obvious)
>     - uploading tarballs
>     - pre-testing against different Linux distribution
>
> I'll can do, what I did previously:
>         - new release commit and tag and create release in github from it
>     - uploading tarballs
>         - release notes for shell API (mostly network shell API)
>
> It'd be big help if Cyril managed to do release notes and the announcement.
>
> Kind regards,
> Petr
>
> [1]
> https://lore.kernel.org/ltp/CAEemH2eSJQ-_30_Y3A567oqBFSOo=1tt7LJMtPq_BodjVNsm8w@mail.gmail.com/
>
>

-- 
Regards,
Li Wang

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

  reply	other threads:[~2023-05-11  5:48 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  9:17 [LTP] LTP release preparations Cyril Hrubis
2023-04-26 10:01 ` Li Wang
2023-04-26 10:08   ` Li Wang
2023-05-08 12:31   ` Li Wang
2023-05-09  9:29     ` Cyril Hrubis
2023-05-10  6:39       ` Li Wang
2023-05-10 13:03         ` Petr Vorel
2023-05-11  5:48           ` Li Wang [this message]
2023-05-15 13:15           ` Cyril Hrubis
2023-05-16  4:58             ` Petr Vorel
2023-05-16  5:35               ` Petr Vorel
2023-05-16  5:46                 ` Petr Vorel
2023-04-26 10:07 ` Teo Couprie Diaz
2023-04-27 14:06 ` Andrea Cervesato via ltp
2023-04-28  9:12 ` Yang Xu (Fujitsu)
2023-05-02 12:18   ` Cyril Hrubis
2023-05-08  5:27     ` Yang Xu (Fujitsu)
2023-05-02 14:37 ` Petr Vorel
2023-05-02 15:14   ` Petr Vorel
2023-05-03  9:35     ` Cyril Hrubis
2023-05-03 16:32       ` Petr Vorel
2023-05-04 10:28         ` Petr Vorel
2023-05-03  9:31   ` Cyril Hrubis
2023-05-03 12:56     ` Petr Vorel
2023-05-04 13:17     ` Petr Vorel
2023-05-04 13:44       ` Cyril Hrubis
2023-05-04 20:37         ` Petr Vorel
2023-05-05 16:55 ` Petr Vorel
2023-05-10 12:59 ` Martin Doucha
2023-05-10 13:15   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2024-01-02 12:53 [LTP] LTP Release preparations Cyril Hrubis
2024-01-02 21:01 ` Petr Vorel
2024-01-10 18:06   ` Petr Vorel
2024-01-11 10:28     ` Petr Vorel
2024-01-03  1:57 ` Petr Vorel
2024-01-03  8:43 ` Yang Xu (Fujitsu)
2024-01-04 12:26 ` Petr Vorel
2024-01-04 12:35   ` Cyril Hrubis
2024-01-18 14:44 ` Cyril Hrubis
2024-01-25 10:17   ` Li Wang
2024-01-25 11:04     ` Cyril Hrubis
2024-01-26 10:40       ` Li Wang
2023-09-13  8:56 Cyril Hrubis
2023-09-13  9:45 ` Martin Doucha
2023-09-13  9:53 ` Andrea Cervesato via ltp
2023-09-13 11:18   ` Cyril Hrubis
2023-09-15  7:07 ` Petr Vorel
2023-09-15 12:03   ` Petr Vorel
2023-09-15 13:46     ` Petr Vorel
2023-09-15 13:02 ` Andrea Cervesato via ltp
2023-09-15 14:01   ` Cyril Hrubis
2023-09-18 11:23 ` Petr Vorel
2023-09-19  9:33   ` Richard Palethorpe
2023-09-26 10:50 ` Petr Vorel
2023-09-28  7:44   ` Li Wang
2023-09-28 17:39     ` Petr Vorel
2023-09-30  0:11   ` Edward Liaw via ltp
2023-09-30  6:22     ` Petr Vorel
2022-05-09 12:50 [LTP] LTP release preparations Cyril Hrubis
2022-05-09 13:51 ` Petr Vorel
2022-05-10  8:36 ` Li Wang
2022-05-10 13:54   ` Cyril Hrubis
2022-05-19 11:42 ` Martin Doucha
2022-05-19 12:11   ` Cyril Hrubis
2022-05-24 13:01 ` Cyril Hrubis
2022-01-05 11:36 [LTP] LTP Release preparations Cyril Hrubis
2022-01-05 14:45 ` Amir Goldstein
2022-01-05 14:53   ` Cyril Hrubis
2022-01-05 16:57     ` Petr Vorel
2022-01-06  9:52 ` xuyang2018.jy
2022-01-07  9:06 ` Li Wang
2022-01-07  9:51   ` Cyril Hrubis
2022-01-14  9:47 ` Cyril Hrubis
2018-04-12 11:35 Cyril Hrubis
2018-04-19 14:17 ` Cyril Hrubis
2018-04-20  3:56   ` Li Wang
2018-04-20 10:49   ` Petr Vorel
2018-04-24 13:39   ` Cyril Hrubis
2018-04-24 21:08     ` Jan Stancek
2018-04-25 13:23       ` Cyril Hrubis
2018-04-25 13:42         ` Jan Stancek
2018-04-25 13:44           ` Cyril Hrubis
2018-04-25 14:11     ` Petr Vorel
2018-05-03  9:28     ` Cyril Hrubis
2018-05-03 11:41       ` Alexey Kodanev
2018-05-03 12:06       ` Petr Vorel
2018-05-11 12:17       ` Cyril Hrubis
2016-01-05 15:36 [LTP] LTP release preparations Cyril Hrubis

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=CAEemH2eqtdEjoopsX0gsWgu5z8s6hgcTVAXM85t2n5a4ccYDVg@mail.gmail.com \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --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.