From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP Release planning
Date: Wed, 15 May 2024 12:11:42 +0200 [thread overview]
Message-ID: <ZkSKXjFayALEdnl8@yuki> (raw)
In-Reply-To: <4c039089-2ac4-4c27-8969-cbac320ae90b@suse.cz>
Hi!
> > As usuall we are supposed to produce a release at the end of the next
> > month, so let me start with the call for patches that should be
> > included. I do plan to look at the patchwork next week and try to review
> > and merge as much as possible, however if there is anything that I
> > shouldn't really miss, please let me know.
>
> Hi, I've just sent a small update to the tcindex01 test that fixes test
> failures due to blacklisted tcindex module. It'd be nice to have it in
> the next release.
Will have a look.
Also I do plan to start with the git freeze and pre-release testing next
week, so if there is anything else that should be considered for the
release, please make know ASAP.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-15 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 8:33 [LTP] LTP Release planning Cyril Hrubis
2024-04-26 8:57 ` Andrea Cervesato via ltp
2024-04-27 4:15 ` Li Wang
2024-05-15 9:52 ` Martin Doucha
2024-05-15 10:11 ` Cyril Hrubis [this message]
2024-05-15 14:33 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 12:04 [LTP] LTP release planning Cyril Hrubis
2021-09-08 12:04 ` Cyril Hrubis
2021-09-14 12:01 ` Cyril Hrubis
2021-09-14 12:01 ` Cyril Hrubis
2021-09-20 6:41 ` Joerg Vehlow
2021-09-20 7:39 ` Cyril Hrubis
2021-09-20 7:41 ` Joerg Vehlow
2021-09-20 8:09 ` Cyril Hrubis
2021-09-20 8:11 ` Cyril Hrubis
2021-09-27 10:27 ` 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=ZkSKXjFayALEdnl8@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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