From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Tarkan Erimer" <tarkan@netone.net.tr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 16:37:02 +0200 [thread overview]
Message-ID: <6101e8c40805210737r487f037et1e1c9ff1bacf526a@mail.gmail.com> (raw)
In-Reply-To: <48341ED5.7060508@netone.net.tr>
On 5/21/08, Tarkan Erimer <tarkan@netone.net.tr> wrote:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
now:
linux-2.6.x -> linux-2.6.(x+1)-rcY -> linux-2.6.(x+1)
\->2.6.x.y
\->2.6.(x+1).y
\->2.6.x.(y+1)-rc1->2.6.x.(.y+1)
\->2.6.x.(y+1)-rc1->2.6.x.(.y+1)
your idea:
linux-2.6.x -> linux-2.6.(x+1)-rcY -> linux-2.6.(x+1)
\->2.6.x.y
\->2.6.(x+1).y
\->2.6.x.(y+1)-test1->2.6.x.(.y+1)
\->2.6.x.(y+1)-test1->2.6.(x+1).(.y+1)
only the namig is was other, rc -> test,
--
Thanks,
Oliver
prev parent reply other threads:[~2008-05-21 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 13:08 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
2008-05-22 6:46 ` Tarkan Erimer
2008-05-21 19:55 ` Rik van Riel
2008-05-21 14:37 ` Oliver Pinter [this message]
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=6101e8c40805210737r487f037et1e1c9ff1bacf526a@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--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 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®