The future of Chora

[Jon Parise]

I'm going to propose a plan for the future of Chora:

Clean up the existing code where possible and implement the
caching system to boost performance.  The reference issue in
CVSlib should also be addressed.  Other ideas such as the
PATH_INFO change and registry integration should also be
completed.  Once this is done, branch this code as Chora 1.0.  A
lot more people use CVS than the other RCS's, so this will give
people a solid release to use for a long while.

For Chora 2.0, start examining the abstraction layer for
difference RCS backends.  I realize this is really cool stuff,
and everyone wants to see it get done, but it's going to take
time, and I think that Chora is a good enough product that it
merits a full 1.0 release before this work starts and
destabilizes the code base.

Luxor work can be aligned along this schedule, too, but I'm not
too intimate with those details (yet).

-- 
Jon Parise (jon@csh.rit.edu)  .  Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/  :  Computer Science House Member