stability of CVS

[Stephen]

Jon,
It's been my experience so far that the current cvs has changed so  
much and fixed so many things compared to the latest stable, that you  
should go with cvs. It has also been my experience that due to the  
high level of activity on this project, any major problems with cvs  
are usually looked at and fixed very quickly.
I've gone the route of cvs, and alerted my users that it's in  
development. I have IMP set up so they can have a choice for now.


Regards,
Stephen


On 17-Jan-06, at 8:27 PM, Jon Daley wrote:

>
> Hi.  This looks like an excellent piece of software.  I have shown  
> it to a couple people who care about design sorts of things, and  
> they were quite impressed.
>
>
>
> I see the don't-use-the-cvs-version-unless-you-want-to-have-broken- 
> email warning on the sourceforge page, and I am wondering how much  
> you mean it.  (:
>
>
>
> I am willing to put up with some instability, but I want it to work  
> most of the time.  Should I stick with the official releases?  I am  
> familiar with cvs (and svn - glad to hear that you are converting  
> over sometime soon) and comfortable working on code.
>
>
>
> Do you have a suggestion?
>
>
>
> -- 
>
> Jon Daley
>
> http://jon.limedaley.com/
>
>
>
>