From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Cyril Hrubis" <chrubis@suse.cz>, <ltp@lists.linux.it>
Subject: Re: [LTP] LTP release preprations
Date: Wed, 28 Jan 2026 10:13:01 +0100 [thread overview]
Message-ID: <DG03V1ZOO5Z5.2R0ON903EMW93@suse.com> (raw)
In-Reply-To: <aWjZX0fsrTJMqq49@yuki.lan>
Hi!
On Thu Jan 15, 2026 at 1:11 PM CET, Cyril Hrubis wrote:
> Hi!
> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.
>
> As for me I'm going to (hopefully) finalize the ground rules patch and
> send another version today.
There's one more thing to do and it's to push a new version of kirk a
minor fix. LTP should update it accordingly.
I didn't see any issue with kirk so far, so we should do this now before
the release, WDYT?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-28 9:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 12:11 [LTP] LTP release preprations Cyril Hrubis
2026-01-15 12:53 ` Li Wang via ltp
2026-01-15 13:52 ` Cyril Hrubis
2026-01-16 1:45 ` Li Wang via ltp
2026-01-16 7:20 ` Petr Vorel
2026-01-22 10:38 ` Jan Stancek via ltp
2026-01-22 11:26 ` Li Wang via ltp
2026-01-16 8:18 ` Andrea Cervesato via ltp
2026-01-22 8:53 ` Petr Vorel
2026-01-22 12:33 ` Martin Doucha
2026-01-26 8:44 ` Andrea Cervesato via ltp
2026-01-27 13:06 ` Cyril Hrubis
2026-01-27 13:25 ` Petr Vorel
2026-01-28 1:59 ` Li Wang via ltp
2026-01-28 7:21 ` Petr Vorel
2026-01-28 0:57 ` Li Wang via ltp
2026-01-28 10:52 ` Martin Doucha
2026-01-28 11:24 ` Ricardo Branco
2026-01-30 9:51 ` Cyril Hrubis
2026-01-28 9:13 ` Andrea Cervesato via ltp [this message]
2026-01-28 9:54 ` Li Wang via ltp
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=DG03V1ZOO5Z5.2R0ON903EMW93@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@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