From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "tytso@mit.edu" <tytso@mit.edu>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Maintainer's Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 17:42:33 +0000 [thread overview]
Message-ID: <1509385352.3660.35.camel@wdc.com> (raw)
In-Reply-To: <20171029100816.pmq5dpmck4cclmdw@thunk.org>
On Sun, 2017-10-29 at 06:08 -0400, Theodore Ts'o wrote:
> Please reply to this thread if you have any comments about how we can
> organize the Maintainer's Summit for next year. Given that Linus
> seemed fairly happy with how things went, it's likely we will stick
> with the same format for next year, but if there are any details about
> how we could do things better, I'd greatly appreciate them.
Something Linus was very clear about is that regressions are not acceptable.
The best way I know to reduce the number of regressions is to increase the
efforts on automatic testing. Should the number of tests that is run by the
zero-day testing infrastructure be increased? Should more tests be added?
Should the documentation that is available on
https://01.org/lkp/documentation/0-day-test-service perhaps be moved
elsewhere, e.g. inside that repository? Do we need a link on kernel.org or
in the kernel documentation to that project?
Thanks,
Bart.
next prev parent reply other threads:[~2017-10-30 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 10:08 Theodore Ts'o
2017-10-30 16:29 ` Bart Van Assche
2017-10-30 16:32 ` Dan Williams
2017-10-30 18:45 ` Mimi Zohar
2017-10-30 17:42 ` Bart Van Assche [this message]
2017-10-30 21:03 ` Theodore Ts'o
2017-10-30 21:20 ` Greg KH
2017-10-30 21:24 ` Konstantin Ryabitsev
2017-10-30 21:27 ` James Bottomley
2017-10-30 21:27 ` Bart Van Assche
2017-10-30 21:43 ` greg
2017-10-30 22:36 ` Julia Lawall
2017-10-30 18:46 ` Takashi Iwai
2017-10-30 23:10 ` Jiri Kosina
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=1509385352.3660.35.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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