All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tarkan Erimer <tarkan@netone.net.tr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 16:08:37 +0300	[thread overview]
Message-ID: <48341ED5.7060508@netone.net.tr> (raw)

Hi,

After long discussions about kernel release methodology, an idea has 
came to ( Any comments welcomed :-) ) my mind :

-  2 weeks of merge window for each "rc" releases should remain the same .
- When decided the 2.6.xx-rcx is ready to become 2.6.xx, it should be 
2.6.xx-test1 instead of 2.6.xx
- Chris Wright (or whoever will handle these "testX" maintaining) can 
maintain these "testX" releases as like 2.6.x.y maintaining.
- After releasing the "testX" releases, the new kernel release process 
should start.
- When Chris decided it is stable enough, it should release as 2.6.xx 
(stable).
- Of course, 2.6.x.y releases follows then as usually.

Please share your opinions. Thanks :-)

Tarkan

             reply	other threads:[~2008-05-21 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 13:08 Tarkan Erimer [this message]
2008-05-21 13:38 ` Suggestion About Kernel Releases Arjan van de Ven
2008-05-21 13:48   ` Pekka Enberg
2008-05-21 14:00     ` Tarkan Erimer
2008-05-21 14:32       ` Mike Snitzer
2008-05-21 15:15         ` Tarkan Erimer
2008-05-21 15:26           ` Pekka Enberg
2008-05-24  3:11             ` Enrico Weigelt
2008-05-21 13:59   ` Tarkan Erimer
2008-05-21 14:28     ` Arjan van de Ven
2008-05-21 14:50       ` Tarkan Erimer
2008-05-21 15:12         ` Arjan van de Ven
2008-05-21 17:31     ` Chris Wright
2008-05-22  6:46       ` Tarkan Erimer
2008-05-21 19:55     ` Rik van Riel
2008-05-21 14:37 ` Oliver Pinter

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=48341ED5.7060508@netone.net.tr \
    --to=tarkan@netone.net.tr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.