From: david@lang.hm
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, DRI <dri-devel@lists.freedesktop.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@suse.de>
Subject: Re: (Short?) merge window reminder
Date: Tue, 24 May 2011 11:55:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1105241147150.23692@asgard.lang.hm> (raw)
In-Reply-To: <20110524183405.GA14493@citd.de>
On Tue, 24 May 2011, Matthias Schniedermeyer wrote:
> On 23.05.2011 13:33, Linus Torvalds wrote:
>> On Mon, May 23, 2011 at 12:20 PM, Ingo Molnar <mingo@elte.hu> wrote:
>>>
>>> I really hope there's also a voice that tells you to wait until .42 before
>>> cutting 3.0.0! :-)
>>
>> So I'm toying with 3.0 (and in that case, it really would be "3.0",
>> not "3.0.0" - the stable team would get the third digit rather than
>> the fourth one.
>
> What about strictly 3 part versions? Just add a .0.
>
> 3.0.0 - Release Kernel 3.0
> 3.0.1 - Stable 1
> 3.0.2 - Stable 2
> 3.1.0 - Release Kernel 3.1
> 3.1.1 - Stable 1
> ...
>
> Biggest problem is likely version phobics that get pimples when they see
> trailing zeros. ;-)
since there are always issues discovered with a new kernel is released
(which is why the -stable kernels exist), being wary of .0 kernels is not
neccessarily a bad thing.
I still think a date based approach would be the best.
since people are worried about not knowing when a final release will
happen, base the date on when the merge window opened or closed (always
known at the time of the first -rc kernel)
in the thread on lwn, people pointed out that the latest 2.6.32 kernel
would still be a 2009.12.X which doesn't reflect the fact that it was
released this month. My suggestion for that is to make the X be the number
of months (or years.months if you don't like large month values) between
the merge window and the release of the -stable release. This would lead
to a small problem when there are multiple -stable releases in a month,
but since that doesn't last very long I don't see a real problem with just
incramenting the month into the future in those cases.
David Lang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-24 18:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:13 Linus Torvalds
2011-05-23 19:20 ` Ingo Molnar
2011-05-23 20:33 ` Linus Torvalds
2011-05-23 20:52 ` Alexey Zaytsev
2011-05-25 14:12 ` Boaz Harrosh
2011-05-25 22:21 ` Tony Luck
2011-05-26 16:38 ` Boaz Harrosh
2011-05-23 21:41 ` Yuhong Bao
2011-05-23 21:59 ` Oliver Pinter
2011-05-23 22:21 ` Greg KH
2011-05-23 23:40 ` Matthew Wilcox
2011-05-23 23:10 ` jonsmirl
2011-05-23 23:17 ` Ted Ts'o
2011-05-23 23:21 ` Randy Dunlap
2011-05-23 23:23 ` H. Peter Anvin
2011-05-23 23:33 ` Linus Torvalds
2011-05-24 2:01 ` Ingo Molnar
2011-05-24 7:55 ` Arnd Bergmann
2011-05-24 14:41 ` Alan Cox
2011-05-24 14:48 ` Ralf Baechle
2011-05-23 23:53 ` Phil Turmel
2011-05-24 2:11 ` Ingo Molnar
2011-05-24 18:06 ` Lisa Milne
2011-05-24 20:59 ` Zimny Lech
2011-05-25 15:03 ` Martin Nybo Andersen
2011-05-24 18:34 ` Matthias Schniedermeyer
2011-05-24 18:55 ` david [this message]
2011-05-24 21:25 ` Andy Lutomirski
2011-05-25 12:52 ` Jiri Kosina
2011-05-24 23:00 ` Hans-Peter Jansen
2011-05-23 19:22 ` Greg KH
2011-05-23 20:04 ` James Bottomley
2011-05-23 19:25 ` Thomas Gleixner
2011-05-23 20:21 ` Randy Dunlap
2011-05-23 21:02 ` Steven Rostedt
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=alpine.DEB.2.02.1105241147150.23692@asgard.lang.hm \
--to=david@lang.hm \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=ms@citd.de \
--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