production ready?

[rb...@connected.com]

Is anyone using subversion in a production environment?  Also, does anyone
have an estimate as to when the official release of version 1.0 will take
place? 

I'm looking for a new scm system for my company and subversion sounds good.

Thanks,
Ryan

Re: production ready?

[cm...@collab.net]

rbraswell@connected.com writes:

> Is anyone using subversion in a production environment?

I guess you could say that the Subversion team is using Subversion in
a production environment.

> I'm looking for a new scm system for my company and subversion
> sounds good.

If you think it *sounds* nice, you should see it dance! :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: production ready?

[John Goerzen <jg...@complete.org>]

rbraswell@connected.com writes:

> Is anyone using subversion in a production environment?  Also, does anyone
> have an estimate as to when the official release of version 1.0 will take
> place? 
>
> I'm looking for a new scm system for my company and subversion sounds good.

I have been running several Subversion repositories since last July at
http://svn.complete.org.  They are the only repositories for several
of the programs I write.  I have not yet lost any data with Subversion
in any way.

I have experienced some lockups and some conditions that require
"svnadmin recover".  However, as I said, no data was ever lost.
Additionally, the Berkeley DB has a fairly nice rollback feature to
recover from any corrupting influence.

Having said all that, I must also say that I've experienced problems
with cvs.  I have been using Subversion this long because of my simple
belief that cvs just isn't up to snuff for even my relatively simple
needs.  Basic things like renaming files are already handled far
better in Subversion than in CVS, and this is bound to improve more
yet.  I have on occasion encountered data loss from CVS, most notably
due to problems with branching, tagging, and binary files.  (Some of
that may be attributable to human error; however, Subversion's design
protects against that too.)

So in a nutshell, I'd say it's no worse than CVS :-)

-- John


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: production ready?

[Stephen Clouse <st...@theiqgroup.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Apr 21, 2003 at 03:11:45PM -0400, rbraswell@connected.com wrote:
> Is anyone using subversion in a production environment?

We have been using it in full production since last July.  Our developer group
is small (8 full-time) but farily active.  Switching to Subversion was a rather
daring move at the time, but we were sick enough of CVS's shortcomings that we
went ahead with it.  We have had a few problems associated with our early
adoption, but that's nothing that good nightly backups can't fix.

The problems we had were more because of Subversion's alpha state at that time
than anything.  Subversion has become far less volatile to date, so I'd say it's
worth your consideration.  Since about 0.18 or so it's been essentially flawless
for our purposes.

- -- 
Stephen Clouse <st...@theiqgroup.com>
Senior Programmer/DBE, Core Technology Developer
The IQ Group, Inc. <http://www.theiqgroup.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+pIzAA4aoazQ9p2cRAnK4AJ9gWSJoAz/KeLUYUkf4VfU3sVVDlgCeKvh1
CicmE7f8CLODZPJAvKNZvOM=
=RfkP
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org