From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.28-rc8
Date: Wed, 10 Dec 2008 21:09:55 -0800 [thread overview]
Message-ID: <20081210210955.36fa2965@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0812101651130.3340@localhost.localdomain>
On Wed, 10 Dec 2008 17:04:39 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Nothing overly exciting here. Lots of small things, mostly in drivers
> (with some defconfig updates for m68k and mips making the diffs
> bigger).
>
> There's some uncomfortably big changes to the intel DRI code, but
> most of that is all about fixes to the new i916 "GEM" code that is
> only used by development X servers, and is a new feature, so it
> shouldn't be able to cause regressions.
>
> Perhaps more interesting is simply the release scheduling issue. I'm
> getting slowly ready to do a real 2.6.28, but I don't think anybody
> really wants the merge window to be around the holidays. So the
> question is really whether to
>
> (a) just make the -rc's go on a few more weeks, and do 2.6.28 after
> xmas
>
> I like this, because alledgely people are debugging things, and
> we'd get a more stable 2.6.28.
>
> or
>
> (b) release in a week or two, but just allow for possibly extending
> the merge window due to people being drunk on eggnog..
>
> I like this because let's face it, we get more and better bug
> information after releases, and everything _should_ be ready for
> merging *before* the merge window anyway.
>
if you go for option (b) I would suggest doing an -rc in the middle, or
at least some snapshot release, to act as anchor point for the second
wave... maybe even a day or two of quiet around that to give people
time to regroup.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-12-11 5:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 1:04 Linux 2.6.28-rc8 Linus Torvalds
2008-12-11 2:37 ` Gabriel C
2008-12-11 7:19 ` Eric Anholt
2008-12-11 16:07 ` Frans Pop
2008-12-11 16:22 ` Linus Torvalds
2008-12-11 16:35 ` Ingo Molnar
2008-12-11 17:05 ` Linus Torvalds
2008-12-11 20:36 ` Ingo Molnar
2008-12-11 20:46 ` Pekka Enberg
2008-12-11 21:34 ` Suresh Siddha
2008-12-12 8:24 ` Ingo Molnar
2008-12-12 15:57 ` Arjan van de Ven
2008-12-12 16:11 ` Linus Torvalds
2008-12-13 17:15 ` Arjan van de Ven
2008-12-16 22:34 ` Ingo Molnar
2008-12-11 5:09 ` Arjan van de Ven [this message]
2008-12-11 7:57 ` Nick Piggin
2008-12-11 8:07 ` Andrew Morton
2008-12-11 8:45 ` Nick Piggin
2008-12-12 3:02 ` Andrew Morton
2008-12-12 3:07 ` Nick Piggin
2008-12-12 3:39 ` Andrew Morton
2008-12-11 8:06 ` Willy Tarreau
2008-12-11 8:40 ` Joerg Roedel
2008-12-11 22:57 ` Theodore Tso
2008-12-11 23:12 ` Mike Travis
2008-12-11 9:26 ` Jean Delvare
2008-12-11 10:38 ` Frederik Deweerdt
2008-12-11 16:59 ` Andrew Morton
2008-12-11 13:00 ` Sam Ravnborg
2008-12-11 13:23 ` Paolo Ciarrocchi
2008-12-11 13:44 ` Alexey Zaytsev
2008-12-11 13:48 ` Ingo Molnar
2008-12-11 15:20 ` Pavel Machek
2008-12-11 15:29 ` David Howells
2008-12-12 3:19 ` David Miller
2008-12-12 5:40 ` Linus Torvalds
2008-12-12 7:54 ` Joerg Roedel
2008-12-12 15:48 ` Alan Cox
2008-12-11 20:12 ` Rafael J. Wysocki
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=20081210210955.36fa2965@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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