Releasing 1.02 and 1.1-pre1.

[Rob Landley]

Okay guys, here's the deal:

Erik doesn't do releases unless seriously provoked.  I put together 1.01 and 
there's a call for a follow-on to that because of the vi bug.  Fine.  I'll 
start work on a 1.0.2 release after Linucon (which is this weekend).

I would like 1.0.2 to be the last -stable release before 1.1 ships.  It's 
certainly the last one I'm planning to do (although there might be a 1.0.2.1 
if obvious bugs crop up.)

To that end, I'm going to start putting a 1.1-pre1 release together after 
1.02, and I'm considering doing it by just merging a snapshot into the 
current -stable repository and testing it as much as I can manage.

After 1.1-pre1, there will be a "fixes only" period in preparation for 1.1.  
There are all sorts of new features people are working on (I've heard rumbles 
of fuser, for example), but if it's not in the repository when I clone it, 
it's not going in 1.1.  (There will be a 1.2 eventually.  We're not going to 
run out of numbers anytime soon, so don't worry about it.)

I'm hoping to get 1.1.0 out (and yes it will have TWO periods this time) by 
the one year anniversary of the 1.0 release, I.E. January 13.  This gives us 
two full months to stabilize the thing before release, which sounds about 
right considering we're in pretty good shape right now.

If anybody would like to weigh in on this, feel free. :)  I'm going to try to 
cut the 1.0.2 release next week, and 1.1-pre1 should go out the week after 
that.  So if you have pending features you want to go into 1.1, or a lost 
patch we've forgotten about (and there have been plenty) now would be the 
time to bring them up. :)

Yes, sometime between 1.1-pre1 and 1.1.0 we need to go through the bug list 
and close all that stuff.  But that's not blocking for -pre1.

Rob