mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Linux Kernel Development
Date: Mon, 16 Jul 2007 23:04:58 +0200	[thread overview]
Message-ID: <4d8e3fd30707161404u49108231kae05aa80180a8857@mail.gmail.com> (raw)

Hi all,
I'm the author of the document "Introduction to Linux Kernel
Development Process" hosted at
http://linux.tar.bz/articles/2.6-development_process.
Part of the document has been included in Documentation/HOWTO

I was reading  both the documents while I started, again, to think
about how to improve the quality of the vanilla kernels.

Here are a few line of the document I wrote:

---8<------8<------8<------8<------8<------8<------8<------8<------8<---
 --- 2.6.x kernels ---

2.6.x kernels are maintained by Linus Torvalds,
it's development is as follow:
- As soon a new kernel is released a two weeks windows is open, during
  this period of time maintainers can submit big diffs to Linus, usually
  the patched sited in -mm kernels for a few weeks.
  Preferred way to submit big changes is using GIT
  (more information about GIT at http://git.or.cz/ and
  http://www.kernel.org/pub/software/scm/git/docs/tutorial.html).
- After two weeks a -rc1 kernel is released and now is possible to
  push only patches that do not include new functionalities that could
  affect the stability of the whole kernel. Please note that a whole
  new driver (or filesystem) might be accepted
  after -rc1 because there is no risk of causing regressions with
  such a change
- A new -rc is released whenever Linus deems the current git
 (the kernel's source management) tree to be in a reasonably sane state
  adequate for testing. The goal is to release a new -rc kernel every week.
- Process continues until the kernel is considered "ready", the
  process should last around 6 weeks ( 6 kernels per year should be
  released) an usually includes 4/5 rc releases.
---8<------8<------8<------8<------8<------8<------8<------8<------8<---

The sentence "Process continues until the kernel is considered "ready"
" should probably be changed in order to reflect the usage of the
"regression list" that Adrian and then Michal were used to maintain.

Is there a "stable" place were users can read/comment/modify the list?
Wasn't Google interested in employee a person to take care of
regression/bug report? (Yes, if there is an open position I would be
interested in applying ;-).

Thanks!

Regards,
-- 
Paolo

             reply	other threads:[~2007-07-16 21:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 21:04 Paolo Ciarrocchi [this message]
2007-07-16 21:34 ` Michal Piotrowski
2007-07-16 21:37   ` Paolo Ciarrocchi
     [not found] <CAK8ka9y1VhMzS0X2GSEg4AQzSMPwOkS3HQxBuX4t-Rp-_OwDow@mail.gmail.com>
2011-08-22  4:51 ` linux kernel development Niloofar Fazlollahi
2011-08-22  4:53   ` Américo Wang
  -- strict thread matches above, loose matches on Subject: below --
2006-06-03 13:36 Linux " Paolo Ciarrocchi
2006-06-03 18:28 ` Horst von Brand
2006-06-04 10:00   ` Paolo Ciarrocchi
2006-06-04 10:30     ` Paolo Ciarrocchi
2006-06-04 23:05       ` Horst von Brand
2006-06-05 11:39         ` Paolo Ciarrocchi
2006-06-05 14:58           ` Steven Rostedt
2006-06-05 20:52             ` Paolo Ciarrocchi
2006-06-05 17:38           ` Horst von Brand
2006-06-05 20:51             ` Paolo Ciarrocchi
2006-06-06 19:22   ` Paolo Ciarrocchi
2006-06-06 22:09     ` Horst von Brand
2006-06-07 21:59       ` Paolo Ciarrocchi

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=4d8e3fd30707161404u49108231kae05aa80180a8857@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®