From: "Christopher Friesen" <cfriesen@nortel.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Eric Sandall <eric@sandall.us>, Willy Tarreau <willy@w.ods.org>,
Linus Torvalds <torvalds@osdl.org>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Tony Luck <tony.luck@gmail.com>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: New (now current development process)
Date: Mon, 07 Nov 2005 11:11:26 -0600 [thread overview]
Message-ID: <436F8ABE.9020605@nortel.com> (raw)
In-Reply-To: <m3k6fkxwqe.fsf@defiant.localdomain>
Krzysztof Halasa wrote:
> Eric Sandall <eric@sandall.us> writes:
>>A -final should never be changed from the last -rc. That defeats the
>>purpose of having -rc releases (rc == 'release candidate' ;)).
>
>
> This logic is flawed. RCs are for performing tests. If you don't want
> further tests (for example, tests on previous RC completed and you're
> quite sure new changes introduce no new bugs) you don't need further
> RCs.
How do you ever know that new change introduced no new bugs? Maybe
there was a latent race condition that is activated by timing
differences caused by the new code. Maybe it shifts the spacing of the
code just enough to get hit by a pre-existing trampler. Unless you test
it, you *can't* know.
The safe bet is to simply rename the final -rc with no further changes.
Chris
next prev parent reply other threads:[~2005-11-07 17:12 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 17:26 New (now current development process) Paolo Ciarrocchi
2005-10-29 18:57 ` Tony Luck
2005-10-29 19:51 ` Russell King
2005-10-29 20:28 ` Linus Torvalds
2005-10-29 20:44 ` Akula2
2005-10-29 23:28 ` Greg KH
2005-10-29 22:29 ` Andi Kleen
2005-10-29 22:37 ` Russell King
2005-10-30 19:12 ` Andrew Morton
2005-10-30 21:43 ` Russell King
2005-10-30 22:31 ` Andrew Morton
2005-10-30 22:45 ` Russell King
2005-10-30 22:55 ` Andrew Morton
2005-10-30 23:17 ` Russell King
2005-10-31 0:48 ` Andi Kleen
2005-10-31 0:16 ` Russell King
2005-10-31 1:22 ` Andrew Morton
2005-10-31 2:41 ` Andi Kleen
2005-10-31 6:34 ` Zwane Mwaikambo
2005-10-31 7:07 ` Andrew Morton
2005-10-31 23:58 ` Roman Zippel
2005-11-01 0:05 ` Andrew Morton
2005-11-01 0:13 ` Linus Torvalds
2005-11-01 0:34 ` Andrew Morton
2005-11-01 0:59 ` Grant Coady
2005-11-01 14:08 ` Adrian Bunk
2005-11-01 15:15 ` Nix
2005-11-01 15:26 ` Bill Davidsen
2005-11-02 5:01 ` Roland Dreier
2005-11-02 5:43 ` Linus Torvalds
2005-11-02 5:56 ` Roland Dreier
2005-11-02 6:05 ` Linus Torvalds
2005-11-02 6:15 ` Roland Dreier
2005-11-02 15:54 ` Linus Torvalds
2005-11-02 17:48 ` Dave Jones
2005-11-02 18:12 ` Adrian Bunk
2005-11-02 20:11 ` David Lang
2005-11-02 22:31 ` Sam Ravnborg
2005-11-03 18:54 ` Andi Kleen
2005-11-02 23:11 ` Rob Landley
2005-11-04 22:08 ` Tim Bird
2005-11-04 22:35 ` Andi Kleen
2005-11-04 23:33 ` Tim Bird
2005-11-02 15:41 ` Andreas Kleen
2005-11-01 7:52 ` Russell King
2005-11-01 9:09 ` Rob Landley
2005-11-01 14:15 ` Adrian Bunk
2005-11-01 0:17 ` Roman Zippel
2005-11-01 0:34 ` Jesse Barnes
2005-10-31 1:10 ` Andrew Morton
2005-10-31 5:05 ` Rob Landley
2005-10-31 7:17 ` Andrew Morton
2005-10-31 8:47 ` Rogério Brito
2005-10-31 9:54 ` Andrew Morton
2005-11-02 5:04 ` Martin J. Bligh
2005-10-30 21:32 ` Theodore Ts'o
2005-10-31 0:45 ` Andi Kleen
2005-10-31 0:18 ` Al Viro
2005-10-31 3:14 ` Paul Jackson
2005-10-31 3:34 ` Al Viro
2005-10-31 6:17 ` Paul Jackson
2005-10-31 7:22 ` Andrew Morton
2005-10-31 7:27 ` Al Viro
2005-10-31 8:19 ` Paul Jackson
2005-11-02 4:53 ` Martin J. Bligh
2005-11-02 4:49 ` Martin J. Bligh
2005-10-31 4:52 ` Rob Landley
2005-11-02 14:44 ` Andreas Kleen
2005-10-30 1:12 ` Tony Luck
2005-10-31 6:41 ` Willy Tarreau
2005-11-07 4:54 ` Eric Sandall
2005-11-07 16:12 ` Krzysztof Halasa
2005-11-07 17:11 ` Christopher Friesen [this message]
2005-11-07 17:22 ` Linus Torvalds
2005-11-07 17:28 ` Linus Torvalds
2005-11-07 20:34 ` Willy Tarreau
2005-11-07 18:25 ` Krzysztof Halasa
2005-10-30 0:37 ` Jesper Juhl
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=436F8ABE.9020605@nortel.com \
--to=cfriesen@nortel.com \
--cc=eric@sandall.us \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tony.luck@gmail.com \
--cc=torvalds@osdl.org \
--cc=willy@w.ods.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.