Milestone 2 delay ("Are we there yet, Daddy?")

The bad news first: we're not going to make it, and so we've bitten
the bullet and moved its date all the way to Feb. 1st. (Whoa.)

The reasons are partly developer unavailability -- everyone got
distracted with other tasks, most importantly Jim Blandy -- and partly
an underestimation of the difficulty. With the holiday season
approaching, we would have moved the date to mid-January, but there's
a known conflict for a bunch of developers then, so we just went to
Feb. 1 instead.

The good news: more developers will be working on the filesystem. The
client side is in a fairly stable state, and Ben completely owns that
code now anyway :-). So I'm going to start concentrating on the
repository instead of working copy stuff.

(Obviously, this isn't meant to exclude others from the fs code. I'm
just talking here about paid and semi-paid resources.)

Very sorry about the delay; believe me, I ache for the day when this
thing runs over the network. The filesystem code has made a lot of
progress in the last couple of weeks, but it's just not all the way
there yet. It does seem to be far enough along that adding more
developers will work, though, so that's what we're going to do.

-K
Received on Sat Oct 21 14:36:17 2006