Krzysztof Halasa wrote:
Eric Sandall <[email protected]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
