Date: Thu, 06 Jan 2000 08:28:32 -0500 From: Bakul Shah <bakul@torrentnet.com> To: Julian Elischer <julian@elischer.org> Cc: Darren Reed <darrenr@reed.wattle.id.au>, Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>, louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <200001061328.IAA11896@chai.torrentnet.com> In-Reply-To: Your message of "Thu, 06 Jan 2000 02:14:04 PST." <38746AEC.167EB0E7@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think we should layout a plan of everything that everyone is working
> on
> and try find a natural inflection point. I reallu thing that IPV6 is too
> important to make a release with it "half" implemented.
What would be nice is a table of features versus release in
which they appear. Something like
3.3 3.4 3.x? 4.0 4.1 5.0
hood ornaments x x
tailights p x x
hubcaps x
bigger trunk x
sound system
8 track x
cassette x
fairings
Where x == full support, p == partial support. More complex
features get broken into featurelets. Adjust and publish the
table every few weeks/months to reflect reality -- generally
that means turning an x into p or moving it to the next
column! Separately you lay down a tentative schedule so
people know when to expect what feature + developers have a
target to shoot for and last minute surprises are fewer.
Given the volunteer nature of the project the schedule
will be much more tentative but it is useful nonetheless.
Having said all that, IMHO a 4.0 release with partial IPv6
support would be useful.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001061328.IAA11896>