From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel development cycle
Date: Wed, 22 Nov 2017 11:07:09 +1100 [thread overview]
Message-ID: <20171122000709.GU7472@eros> (raw)
Hi,
Would someone please be able to expound on the stages of the kernel
development cycle.
In particular I would like to learn what a hobbyist kernel developer
should be focusing their attention on during different stages of the
cycle. In particular, what _not_ to do during certain stages of the
cycle.
Jonathan Corbet has mentioned that he is happy to take documentation
patches during the merge window. Are other sub-systems open to patches
during the merge window? My guess is not.
Should one be focusing effort on bug fixing only (as opposed to new
features) during rc1 and rc2?
What about coverity fixes, are these most appreciated during early
release candidates or are they better done against linux-next during
later release candidates (so the bugs don't get into the mainline in the
first place)?
When are new feature patches best submitted?
Or is all this not answerable because each maintainer/subsystem is
different?
Thanks in advance for your thoughts,
Tobin.
next reply other threads:[~2017-11-22 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 0:07 Tobin C. Harding [this message]
2017-11-22 0:39 ` kernel development cycle valdis.kletnieks at vt.edu
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=20171122000709.GU7472@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).