I think it's a good idea, but the question really needs to be answered by oDD & Lantus. Weekly CVS would be enough, or even bi-weekly. I'd like to see a CVS system so as we 'use' the program, then send feedback achnowledging FIXES in the program or to address "broken" code that had worked in previous versions. Then again, I personally don't want either author worrying about the CVSs than contributing to v2.0 It may be more appropriate for the authors to release a pre v2.0 beta, to let everyone get a run down of what has been changed, then address to problems before v2.0 is out, *or* just release v2.0, when it's done of course, then let everyone check for bugs as they use it, then releases fixes to 2.0.
I'm good for any 3 of the options, I'd just prefer what the authors would like to do.
Just my 2 cents.
ejx982