cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Simmons" <>
Subject Re: New CVS?
Date Sun, 19 Oct 2003 17:03:24 GMT
Yes, I have looked at that project. Its no youngster itself having started in
95.Nine years is a long time in the computing world to put a product into
production. In fact it is usually lethal. Given the pace of the industry, a
product needs to hit in a usable version in less than a year to be feasible.

In addition, subversion requires C to code clients to it. This limits the scope
of potential deployment strategies significantly. In addition, C coding is
resource intensive. Sure, it might be marginally faster but it takes a C coder
something near three times as long as a Java developer to get a product to

I have other arguments with subversion as well. It doesn't do multiple projects
well, instead requiring that you create multiple repositories, one for each
project. It also fails to recognize the dichotomy between a file version and a
software version. Seeing revision 5678 on a file that has never been changed is
quite .... strange.

Finally, by subversion's own admission they aren't trying to break ground, but
merely "replace" CVS.

Ultimately I think subversion presents a great source of research for lessons
learned, both good and bad, but does not represent the future.

My vision is of an architecture that is extensible, powerful, efficient and
based upon commonly used standards. (Lets face it, WebDAV is all but dead)

-- Robert

"Yannick Menager" <> wrote in message
> I've been using subversion ( ) for quite
> awhile, and it is really good. light-years better than CVS. And works
> through HTTP proxies :), oh, and there's a tortoisesvn, for the
> tortoisecvs fans ;)
> Robert Simmons wrote:
> > Lets face it, CVS is an OLD product. Furthermore, the development of CVS is
> > almost dead having few releases in recent years. At least this is my
> >
> > What I am doing in polling the community of open source developers as to
> > they think. I am seriously considering starting a project to replace CVS
> > Java technology in the way that Ant has virtually replaced make as a build
> > utility (for good reason).
> >
> > I am curious about the following questions:
> >
> > 1) What do you think about the idea?
> >
> > 2) What lessons do you think can be learned from CVS? Things done badly, not
> > done at all, etc.
> >
> > 3) What features in CVS do you believe should be deprecated and why?
> >
> > 4) What features would you like to see in a replacement to CVS that
> > are not available in CVS?
> >
> > And for the Apache Folk:
> >
> > 5) Would you consider this an interesting project for ASF?
> >
> > I look forward to your answers and comments.
> >
> > -- Kraythe

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message