All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org, jan.kiszka@siemens.com
Subject: 4.4.X-stable and 4.4.X-rt maintainance ends in less than two weeks
Date: Wed, 19 Jan 2022 15:12:10 +0100	[thread overview]
Message-ID: <20220119141210.GA2310@duo.ucw.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]

Hi!

It looks like stable 4.4.X maintainence ends real soon now:
https://www.kernel.org/category/releases.html . I talked to Greg and
it seems like plan is to end it at the beggining of month, rather than
end.

That means we'll be on our own maintaining -cip and -cip-rt versions.

To review our 4.4 branch:

git log --pretty=oneline linux-4.4.y-cip-rebase

We have 757 patches on top of 4.4.216, and there are some 14000
patches between 4.4 and 4.4.216. Going forward, most new patches will
come from upstream.

We do some compile testing, but we only run run-time tests on two
targets:
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/448669210
.

Given that most of work we'll be doing will be maintaining -stable
patches, anyway, I believe it would make sense to step up as official
maintainers of 4.4.X-stable and 4.4.X-rt series. We'll need to do the
work, anyway, keeping -stable and -cip split will not result in much
overhead for us, and this way we'll get a lot of visibility for the
project, and hopefully a lot of additional testing.

Any thoughts?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2022-01-19 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 14:12 Pavel Machek [this message]
2022-01-20  2:26 ` [cip-dev] 4.4.X-stable and 4.4.X-rt maintainance ends in less than two weeks Masami Ichikawa
2022-01-24 14:01   ` 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=20220119141210.GA2310@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.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.