From: Ulrich Hecht <uli@fpond.eu>
To: jan.kiszka@siemens.com,
"Jan Kiszka via lists.cip-project.org"
<jan.kiszka=siemens.com@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"chris.paterson2@renesas.com" <chris.paterson2@renesas.com>,
"masami.ichikawa@cybertrust.co.jp"
<masami.ichikawa@cybertrust.co.jp>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip131
Date: Mon, 13 Apr 2026 10:17:09 +0200 (CEST) [thread overview]
Message-ID: <1743542625.76882.1776068229391@webmail.strato.de> (raw)
In-Reply-To: <52d1c70f-ac3e-4f4c-9593-c20f08d60e9e@siemens.com>
> On 04/13/2026 7:36 AM CEST Jan Kiszka via lists.cip-project.org <jan.kiszka=siemens.com@lists.cip-project.org> wrote:
> Looks like we are phase-shifted on 4.19 between regular (-cip131) and RT
> (-cip130-rt47) again. Was there a particular reason for timing things
> like this?
The release dates kept slipping towards the end of the month because of large 5.10 releases. 5.10.251 was very small, however, so I used the opportunity to release cip130 early to correct for that, and now try to keep release dates in the first half of the month if possible.
CU
Uli
next prev parent reply other threads:[~2026-04-13 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 7:37 [ANNOUNCE] Release v4.19.325-cip131 Ulrich Hecht
2026-04-13 5:36 ` Jan Kiszka
2026-04-13 8:17 ` Ulrich Hecht [this message]
2026-04-13 10:08 ` [cip-dev] " Jan Kiszka
2026-04-13 11:29 ` Pavel Machek
2026-04-13 15:47 ` Jan Kiszka
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=1743542625.76882.1776068229391@webmail.strato.de \
--to=uli@fpond.eu \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka=siemens.com@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.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