I have this totally crazy idea:
What if we could release 1.2 this year?
Not that it really matters whether it comes out before Jan. 1st, of
course. This is just an utterly transparent motivational technique to
get us to concentrate on the 1.2 bugs. There are only 33 of them
left, plus 13 "1.2-consider" issues. With so many active committers,
I'll bet we can plow through them pretty fast. I did #2065 this
weekend, and am working on #2106 right now.
Reminder: when you pick an issue, assign it to yourself then mark it
as started, so others know to pick a different one.
By the way, the current 1.2 list isn't sacred. For the most part
issues are in there because I put them there, and my criterion was
roughly "This is important and it would suck to make another release
with this bug still present." Please feel free to move an issue out
of 1.2 if you think it doesn't belong there, or to swap it with one
from 'unscheduled' if you think that one should be fixed first. My
prioritizations were meant to be helpful, not dictatorial.
Now, no jokes about 1.2 getting bogged down in dueling lawyers and
arguments over whether we should move to a proportional representation
system for voting. As long as the release is sworn in by January
20th, we'll be fine. (With apologies to Jani Averbach.)
Back to #2106,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 1 22:57:38 2004