On Sat, March 17, 2007 10:51 pm, Timo Sirainen <[EMAIL PROTECTED]> said:

> Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm
> still wondering if I should put it there soon and make the release after
> v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD
> features (which shouldn't take too long), do a v1.2 release and only
> then put this code to CVS and make it v2.0..

I vote for first stabilizing the current new CVS HEAD, do a v1.1 release, and 
then put the ssl rewrite into CVS and plan to make that either v1.2 or v2.0.  
That way people will start banging on the new features in current CVS HEAD 
sooner.

Bill

Reply via email to