All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Tarkan Erimer <tarkan@netone.net.tr>
Cc: Arjan van de Ven <arjan@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 10:31:27 -0700	[thread overview]
Message-ID: <20080521173109.GD4018@sequoia.sous-sol.org> (raw)
In-Reply-To: <48342ADC.3030509@netone.net.tr>

* Tarkan Erimer (tarkan@netone.net.tr) wrote:
> To make kernel releases more stable/tested via "testX" series, as recently 
> discussed by David Miller's "Slow DOWN, please!!!" thread.

Arjan already pointed out that this was about the merge window, not the
tail.

> These "testX" 
> releases will give more opportunity and time to test more these new 
> releases. Also, with the aim of the "testX" series, the new kernel release 
> schedules/merge windows will be not slow down. Even, Linus can releases new 
> kernels more quickly. Because, testing purpose should be handled by someone 
> else like Chris did for 2.6.x.y.

(BTW, Greg does 2.6.x.y as well).  What you are missing is that it is not
Greg and I who are doing the bulk of testing for 2.6.x.y.  It's the entire
community, and adding additional stage to the tail or the release cycle
will not increase testing coverage.  History shows it'll just postpone it.

thanks,
-chris

  parent reply	other threads:[~2008-05-21 17:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 13:08 Suggestion About Kernel Releases Tarkan Erimer
2008-05-21 13:38 ` 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 [this message]
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=20080521173109.GD4018@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tarkan@netone.net.tr \
    /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.