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

Re: svn 1.0 in 2006 or now?

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-12-29 17:39:55 CET

solo turn <soloturn99@yahoo.com> writes:
> what are your plans for the 1.0?
>
> my impression after checking the task list for the milestones before
> 1.0 two months ago and now is that continuing like this will end in
> v1.0 in year 2006 or eternity ... as the list is growing, not
> shrinking.

Periodically we do go over the whole bug list and push what we can
past 1.0.

> i know too many people now NOT using svn, cause it is not "finished".
> but this is just not true. it is already more useable than cvs, and
> that is sufficient for most projects and use cases.

Feature-wise, maybe, but not in terms of stability.

Remember that Linux had many users before 1.0, as people gradually
realized that it was getting stable and that Linus was just being
conservative. We're not going to be quite as conservative, perhaps,
but still pretty cautious, because when 1.0 comes out, it needs to be
as safe for your data as CVS.

The main purpose of calling it "1.0" is to say that these interfaces
are relatively stable. If we release 1.0 and then start changing
interfaces, we've missed the point. And it's not as if we're
suffering from a shortage of users or testers right now. Let's worry
about bugs and features, not labels :-).

> or is somebody from the collab-guys, or greg stein without a job
> after 1.0 is released?

No, don't worry, 1.0 has no effect on our jobs. (By the way, Greg
Stein *is* one of the Collab guys.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 29 18:22:50 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.