kernel development cycle

kernel development cycle

[Tobin C. Harding]

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.

kernel development cycle

[valdis.kletnieks at vt.edu]

On Wed, 22 Nov 2017 11:07:09 +1100, "Tobin C. Harding" said:
> 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.

Work on stuff whenever you have time and energy.

Send it upstream after a -rc1 happens.

That should cover 95% of it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171121/65f1df47/attachment.bin