Re: Future CVS Development

[Derek R. Price]

"Kostur, Andre" wrote:

> I see many suggesting floating around on what should be added to CVS (where
> everybody seems to have a different idea of what "should" is).  However, I
> don't recall seeing a roadmap to what is _going to be_ added to CVS.  There
> are a few design decisions that I'd like to know more about, personally.

That's because it isn't really being kept track of in any one place at the
moment.  Much of it is in the archives for this list.  What actually gets into
CVS is some combination of user consensus, developer design, and working code,
with quite a bit of stress put on "working code".  With only a few (read,
"two") developers regularly committing code at the moment, there isn't a whole
lot of time for new development.  I know I can easily blow 16 or 20 hours a
week just answering email on this list and bug-cvs and that's not even counting
the patches I do receive, find necessary or useful, and manage to commit.  Once
I'm done attending to the other projects I try and keep up with and take care
of my job responsibilites, there isn't a whole lot of time left for new code.
I imagine Larry Jones finds himself in similar straits.

I am working on updating cvshome.org with some tools which should ease some of
the administration tasks, but at the moment even that is just yet another time
sink.  Hopefully I will roll that out by the end of the month.

Anyway, discussion is useful, but at some point somebody needs to write the
code and submit it, maybe a few times, until a new working feature is available
which could be committed.

Patches gladly accepted.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden         CollabNet ( http://collab.net )
--
Disneyland: A people trap operated by a mouse