Date: Mon, 15 Jan 1996 05:23:11 -0500
From: Thor Lancelot Simon <tls@NetBSD.ORG>
Message-Id: <199601151023.FAA17318@pain.lcs.mit.edu>
To: netbsd-developers@pain.lcs.mit.edu
Subject: Goals/timeframe for 1.2?
Sender: owner-netbsd-developers@NetBSD.ORG
Precedence: first-class


Has anyone done any thinking about a set of goals and a timefraame for 1.2,
or perhaps 1.1.1?

It would seem to me that perhaps instead of picking a date and deciding that
"we release on day X, regardless of the feature set of the code" it might
not be a bad idea to pick a set of features and decide that "we branch the
new release on the date that feature set X is complete, regardless of the
date".

Personally, I'd like to finish integrating the Kerberos support, which due
to time requirements at my new job will probably not happen until after
Usenix.

Other features I (this is just a personal list) would like to see:  NFS v3,
Minnich's rfork() syscall (I think this is just a drop-in), IPv6, integration
of the various network drivers that FreeBSD has that our i386 port doesn't,
a general exorcism of the NCR driver, and (if possible) integration of the ARM,
sun4m, and Alpha ports into the main source tree.  Oh -- now that there's an
IDE CDROM driver, it wouldn't hurt to have it along for the ride, and the
PCMCIA code too for that matter.

If we're serious about more frequent releases, I think having a 10- or 12-item
checklist of features and perhaps a similar one of bugfixes for the next
minor-version release would be a really good idea.  Remember, these are *minor*
version umbers -- we don't need to fix or enhance everything under the sun
in between them, and in fact if we take the attitude that we do need to we
probably run the risk of doing releases so infrequently that we have a huge
job to do like last time.

Comments?

Thor