On 1/17/12 7:12 PM, Devin Teske wrote:
On Jan 17, 2012, at 7:05 PM, "Matthew D. Fuller"<[email protected]>
wrote:
On Tue, Jan 17, 2012 at 06:49:02PM -0800 I heard the voice of
Julian Elischer, and lo! it spake thus:
5 was not out on a limb for so long because it was a clusterfun, it
was out there because it was a rework of how almost everything in
the kernel worked.
I'm not saying it was a cluster because it was a huge amount of very
deep work; it's because that huge amount of very deep work completely
gated our next release. Now, sure, changing external circumstances
caught us with our pants down, and the tools we were using (like CVS)
made it hard to do anything else. But that just means there were
good reasons why it happened; doesn't make it less clusterfull :)
The two circumstances (giant rework, and long period between major
releases) are duals of each other. If we chop off giant piles of
stuff to do for FreeBSD-next, it's going to take a very long time.
And if we instead just set very long times (Jan 2017 for 10?!
Insanity!) for -next, we're going to end up with giant reworks and
huge differences.
And _both_ faces are very bad. The one means we wait forever for any
new work, and the other means that it takes enormous amounts of work
as a user to transistion across the barrier.
the trouble with 5 was that it had to be all-or-nothing.
there is no such thing as a partly SMP system. (well, not one that
you'd want to run).
the size of the "giant pile of stuff" was not of our choosing.
We could adopt a cycle similar to the Linux Kernel...
Odd numbered releases are "experimental" while even numbered releases are
"stable"
(ducks for flying fruit)
_____________
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[email protected]"
