towards a stable version

I'm glad to see this project increasing pace. In order to make the most out of it, while at the same time keeping order, I have some opinions what we should do:

1. Feature freeze, bugfixes only. From now on.
2. Get a stable version out. 2.0stablebeta. This should occur before we apply patches from Peter McCluskey and John Finlay. Not that their contributions are less interesting, just that we have a lot of new source code on the door step and it can take a while to bugfix all that and I'd rather have a stable version before.

   As Kent just wrote, we're doing our best in cleaning up the current    version, and then I hope we'll release our first 2.0stablebeta.

3. Non-beta release sometime. I prefer not setting any dates.

4. Meanwhile we're fixing bugs for the stable version, we work on the

   feature set for the next version and merge all the code we get from    people that are decided to be part of the hypermail future. There is no    limit to what we can include, but more religous restrictions of what    hypermail should and shouldn't do. We need a lot more discussions around    several of the topics opened up lately.

   We could make sort of a fork in the project to enable us to work on post    2.0 things while we're trying to get 2.0 stable.

I would also like to open the subject about maintaining this project. I don't want this head-of-the-class role I've gotten. I would like to see someone else shouldering the reponsibility of maintaining and leading this project. Kent? Jose? Paul? or why not John or Peter? I want to get back to my former role as a "mere" contributor. The reason for this is my lack of time and my amount of other projects that also require my attention. There's no hurry, but...

-- 
  Daniel Stenberg -- http://www.fts.frontec.se/~dast/