From: Sasha Levin <sashal@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement
Date: Tue, 2 Jul 2019 21:35:57 -0400 [thread overview]
Message-ID: <20190703013557.GQ11506@sasha-vm> (raw)
Hi folks,
If there is interest, I'd like to go over the (minor) changes that went
into the -stable kernel process since last year's MS, the various
automations we now have, and how we have addressed some of the pain
points that came up last year. I'd also love to hear from folks about
the issues they're seeing with the process, and if there's anything we
can do to make it better.
Some of the concerns that were raised during last year's MS (both in the
group session as well as in the hallway track) which we've tried to
address are:
- Commits missing because authors did not respond to Greg's "FAILED:"
mails.
- Concerns about how well -stable kernels are tested.
- "Fixes for fixes" end up being missed.
- Saner AUTOSEL process.
- Tracking of dropped commits.
I found last years feedback very valuable and hopefully have addressed
some of it, hoping for the same this year as well.
--
Thanks,
Sasha
next reply other threads:[~2019-07-03 1:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 1:35 Sasha Levin [this message]
2019-07-03 14:57 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement Laura Abbott
2019-07-05 13:54 ` Michael Ellerman
2019-07-05 14:13 ` Takashi Iwai
2019-07-05 16:17 ` Greg KH
2019-07-05 16:52 ` Sasha Levin
2019-07-05 16:41 ` Mark Brown
2019-07-05 20:12 ` Sasha Levin
2019-07-06 0:32 ` Mark Brown
2019-07-08 11:02 ` Sasha Levin
2019-07-08 11:35 ` Jiri Kosina
2019-07-08 12:34 ` Greg KH
2019-07-08 17:56 ` Sasha Levin
2019-07-08 12:37 ` Mark Brown
2019-07-08 14:05 ` Guenter Roeck
2019-07-08 14:33 ` Takashi Iwai
2019-07-08 15:10 ` Greg KH
2019-07-08 15:18 ` Takashi Iwai
2019-07-08 18:08 ` Sasha Levin
2019-07-08 21:31 ` Jiri Kosina
2019-07-09 15:44 ` Rafael J. Wysocki
2019-07-09 21:05 ` Takashi Iwai
2019-07-09 15:21 ` Laura Abbott
2019-07-08 14:50 ` Mark Brown
2019-07-08 15:06 ` Greg KH
2019-07-08 15:27 ` Mark Brown
2019-07-08 18:01 ` Sasha Levin
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=20190703013557.GQ11506@sasha-vm \
--to=sashal@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).