[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: major design changes...can we

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-05-17 23:02:02 CEST

On Fri, May 17, 2002 at 02:36:22PM -0600, Dean Hiller wrote:
> Hello all,
> I have been developing my own source control system and just foud out
> about subversion today. My system still seems quite orthogonal to yours
> believe it or not. I would like to see one of two things happen.....(if
> possible)
> 1. see these features eventually in subversion

This could always happen after our 1.0 release.

> 2. somehow combine projects(this is no small task seeing how orthogonal the
> two SCM's are)

Not right now, I'm afraid.

The issue is that we're nearing our alpha release which is a "feature
freeze". We should be releasing our 1.0 version by this fall. At the moment,
Subversion is a stable, near-fully-developed version control system. We've
been using Subversion for its own version control system for well over eight
months now.

From your SourceForge project page, I see your project is labeled as
"pre-alpha" and registered just a few months ago. I get the feeling the two
projects are at very different points in their life cycle.

> Is there any interest? Of course, I did not see anywhere on the website
> what language your code is in? Is it in Java?

ANSI C. We're built as a bunch of libraries, so we will have bindings for
those libraries in a bunch of languages (Python, Ruby, and Java have all
been started; SWIG is the workhorse here, and will give us plenty of target
languages). So while Java can be used with Subversion, we're solidly in the
C camp.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 23:00:02 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.