Re: My thoughts on the "new development model"

[William Lee Irwin III]

On Tue, 26 Oct 2004 at 10:37:06 -0700 William Lee Irwin III wrote:
>> It's an existence proof spanning a wide swath of architectures. If
>> you are not seeing similar results, send bugreports.

On Tue, Oct 26, 2004 at 08:00:09PM -0400, Chuck Ebbert wrote:
>   I don't neeed to send in bug reports, there are plenty on l-k
> right now:
>   - LVM is currently broken in 2.6.9-mm1
>   - the RTC and NMI code have a race condition between them
>   - NFS mount won't accept a FQDN over 50 bytes (patch was
>     sent and utterly ignored, then recently reposted)
>   - cdrom driver thinks non-mt. rainier drives are capable

None of the bugs you cite were recently introduced.


On Tue, 26 Oct 2004 at 10:37:06 -0700 William Lee Irwin III wrote:
>> Point releases are in fact updated and maintained. Those updates
>> are given the name of the next point release.

On Tue, Oct 26, 2004 at 08:00:09PM -0400, Chuck Ebbert wrote:
>   Are you saying people who encounter bugs in 2.6.9 should wait for
> 2.6.10?  ...and when they find bugs in _that_ release they should keep
> waiting?  In other words, Zeno was right after all?

Bad idea to try this kind of argument with someone from a domain such as
holomorphy.com. Zeno's mischaracterization of limit arguments was
erroneous and furthermore is irrelevant to discrete models of phenomena,
which don't have indefinite divisibility. In fact, these quantities of
bugs correspond to natural numbers, which yield to infinite descent
arguments, and satisfy descending chain conditions of various kinds.
These are of the form "every descending chain stabilizes", a fortuitous
choice of wording on Artin's part. =)

Upgrade to the later release to get fixes for a given release. This is
not difficult to understand. No point release is "orphaned". The results
of maintaining a point release are the subsequent point releases.

You may also have to face the fact of life that you may actually have to
apply a patch to fix a bug if there's no release to move to yet.


-- wli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/