You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Da...@cwb.ca on 2004/07/21 14:48:59 UTC
Commercial Users of Subversion: LET ME KNOW
Hello, I am new to this list. I have been participating in a 'proof of
concept' project to implement Subversion into our company's computer
environment.
Everything is going fine, and everyone involved is very impressed with
Subversion, except that we have hit a 'snag' in our plans -- the
'conservative' nature of our company will probably refuse the move to
Subversion -- and pick 'CVS' instead -- since we don't want to be the
'first guys on the block' that use Subversion for mission-critical
non-open-source project development.
I have till this Friday to look for evidence that there are 'commercial'
users of Subversion that are using it for 'mission-critical' development
and are happy with it. The 'testimonials' page on the Subversion website
contains lots of good 'open source' users, but I need testimonials from
'commercial' users.
If you think you can help me, please let me know ASAP! I am desperate! :)
Thanks!
Dare
Re: Commercial Users of Subversion: LET ME KNOW
Posted by William Nagel <bi...@stagelogic.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I know it's after Friday, so this may not be any use to you anymore,
but I just got to your email, and figure if nothing else this may help
others in the same situation.
I'm the technology lead for a small linux-based development company.
We've been using Subversion since I lead a changeover from CVS shortly
after SVN became self-hosting. It has been rock-solid, and to date
we've never lost a single revision. The migration from CVS was
seamless, and we were able to quickly eliminate our CVS repository
completely. We've also found its flexibility to be invaluable in
supporting rapid changes of direction on a project, as well as a
variety of development processes, depending on the needs of individual
projects. If you use any XP-style development procedures, CVS will be
a boat anchor around the rest of your process.
In addition to lots of experience bending SVN to my will in a rapidly
evolving development environment, I'm also currently working on a book
about using SVN as a part of the software development process. The
book is still in a relatively early stage, but I've done a lot of work
on it related to how SVN can fit into both a corporate and open source
process. If there's anything I can do to help you or anyone else
convince their own powers-that-be of the usefulness of SVN in a
particular environment, feel free to email me privately, in addition to
anything you may send to the SVN list.
- -Bill Nagel
On Jul 21, 2004, at 9:48 AM, Darren_Enns@cwb.ca wrote:
>
> Hello, I am new to this list. I have been participating in a 'proof
> of concept' project to implement Subversion into our company's
> computer environment.
>
> Everything is going fine, and everyone involved is very impressed with
> Subversion, except that we have hit a 'snag' in our plans -- the
> 'conservative' nature of our company will probably refuse the move to
> Subversion -- and pick 'CVS' instead -- since we don't want to be the
> 'first guys on the block' that use Subversion for mission-critical
> non-open-source project development.
>
> I have till this Friday to look for evidence that there are
> 'commercial' users of Subversion that are using it for
> 'mission-critical' development and are happy with it. The
> 'testimonials' page on the Subversion website contains lots of good
> 'open source' users, but I need testimonials from 'commercial' users.
>
> If you think you can help me, please let me know ASAP! I am
> desperate! :)
>
> Thanks!
>
> Dare
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBBVWjSwe0AHUdEwQRAr8cAKDVWwA5XnXKI7Jk6KgqBgC2UGzgOwCghRwd
I9YYw9sUKL9PRbXZLaIlbgk=
=yGPn
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Felix Collins <fe...@keyghost.com>.
Darren_Enns@cwb.ca wrote:
> If you think you can help me, please let me know ASAP! I am desperate! :)
We are a small company dealing mostly with embedded systems. We
migrated to SVN from.... no source control at all! The only problem we
have had so far was splitting a single repository with multiple projects
into multiple repositories. The svndumpfilter doesn't seem to be worth
the disk space to store it. SVN has been fairly easy to administer. I
have been involved in using PVCS and MS Source Safe in the past and SVN
seems easier and more flexible than either (as well as (perhaps because
of) being open source). Remote access is a huge bonus. We have a
contractor working overseas who connects using https:. This was easy to
set up compared to MS Source off Site which I have heard other
contractors refer to as "Source of Sh*te". ;-)
Good luck and get your overall layout well thought out before installing.
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Ross Mark <ro...@controllingedge.com.au>.
Darren_Enns@cwb.ca wrote:
> I have till this Friday to look for evidence that there are
> 'commercial' users of Subversion that are using it for
> 'mission-critical' development and are happy with it. The
> 'testimonials' page on the Subversion website contains lots of good
> 'open source' users, but I need testimonials from 'commercial' users.
For my own company Controlling Edge and at one of my customers S4
Technology (www.s4-technology.com) I have been running subversion since
0.17 and have never looked back. While there were a few issues initially
we have never lost anything and currently have around 20 repositories
containing everything from source code, documentation to complete
product installations. We use subversion to install and upgrade the
software on our servers. Once we copy the svn client onto the box the
entire installation is a simple svn co plus the asvn to restore
symlinks, devices and file permissions. Upgrading between releases with
svn is great as it automatically merges any changes to local
configuration files with new entries for the latest version. We even use
svn to store file system images for our embedded devices (linux file
system). Currently we have to check out the svn image on a server and
then downloaded to our embedded device via rsync. We don't have the
memory for a full svn client nor the disk space for the working copy but
one day we will write our own svn client that can just do the checkout
without the need for the wc support files or the memory overhead.
For the past 9 years I had been installing CVS at customer sites that
required version control and wouldn't hesitate now to recommend SVN instead.
Ross Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Greg Hudson <gh...@MIT.EDU>.
On Sat, 2004-07-24 at 13:12, Branko Čibej wrote:
> >>5. I'm not sure what this would be called, but it would be very useful
> >>for us to be able to query a list of files/revisions that have a
> >>property set to a certain value.
> You can't do this efficently today. We don't have any kind of property
> index, so you'd have to walk the whole tree all the way back to r1 to
> return such a list. Equivalent in time to dumping the repository.
I don't think it's quite that bad, since we don't use diffy storage for
property lists.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Branko Čibej <br...@xbc.nu>.
C. Michael Pilato wrote:
>Ron Bieber <ro...@bieberlabs.com> writes:
>
>
>>5. I'm not sure what this would be called, but it would be very useful
>>for us to be able to query a list of files/revisions that have a
>>property set to a certain value. For example, "give me all files where
>>prop:defectnumber is 100". I know this type of functionality was
>>discussed briefly in relation to tagging but I would use it in a
>>completely different way so this implementation would have to be
>>general.
>>
>>
>
>Ah, I think I must have missed this suggestion in the past. I can
>certainly see the utility of such a feature. Do you envision this
>being something more than you can already do with shell tools? Want
>me to write you a Python-bindings-using script to do this for you?
>:-)
>
>
You can't do this efficently today. We don't have any kind of property
index, so you'd have to walk the whole tree all the way back to r1 to
return such a list. Equivalent in time to dumping the repository.
Yes, of course you can do this with shell tools...
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Ron Bieber <ro...@bieberlabs.com>.
<snip>
> This little script will search your working copy for a given property.
> Searching revisions for revision props is almost as trivial -- you
> just use client.svn_client_revprop_list(), and cycle through the range
> of revisions you want to search (at a cost of some network turnarounds
> per revision, of course).
>
<snip>
Thanks, this is just what I was looking for. I was looking to store
things in revision properties, so the additional point in the right
direction is appreciated as well ... ;>) .
I seem to be having issues with my 1.1rc1 bindings that I have to debug,
but I did run this with my 1.0.5 bindings and it worked fine.
Re: Commercial Users of Subversion: LET ME KNOW
Posted by "C. Michael Pilato" <cm...@collab.net>.
Ron Bieber <ro...@bieberlabs.com> writes:
> > Ah, I think I must have missed this suggestion in the past. I can
> > certainly see the utility of such a feature. Do you envision this
> > being something more than you can already do with shell tools? Want
> > me to write you a Python-bindings-using script to do this for you?
> > :-)
> >
>
> This would be really helpful, if nothing else to give me an idea as to
> how to do these kinds of things myself. I'd love to be able to
> contribute tools we write around Subversion at some point that prove
> useful to us managing our build, but I'm not an SVN API god yet ... ;>)
Ask and ye shall receive... you have *GOT* to love Python language
bindings, man. Net coding an smoke-testing time was about 15
minutes.
This little script will search your working copy for a given property.
Searching revisions for revision props is almost as trivial -- you
just use client.svn_client_revprop_list(), and cycle through the range
of revisions you want to search (at a cost of some network turnarounds
per revision, of course).
--------------------------------------------------------------------------
#!/usr/bin/python2
import sys
import string
import os.path
from svn import core, client
def find_props(pool, prop_name, wc_path):
revision = core.svn_opt_revision_t()
revision.kind = core.svn_opt_revision_working
ctx = client.svn_client_ctx_t()
providers = []
providers.append(client.svn_client_get_simple_provider(pool))
providers.append(client.svn_client_get_username_provider(pool))
providers.append(client.svn_client_get_ssl_server_trust_file_provider(pool))
providers.append(client.svn_client_get_ssl_client_cert_file_provider(pool))
providers.append(client.svn_client_get_ssl_client_cert_pw_file_provider(pool))
ctx.auth_baton = core.svn_auth_open(providers, pool)
ctx.config = core.svn_config_get_config(None, pool)
props = client.svn_client_proplist(wc_path, revision, 1, ctx, pool)
for prop in props:
if prop[1].has_key(prop_name):
print prop[0]
if __name__ == "__main__":
argc = len(sys.argv)
if argc < 2 or argc > 3:
print "Usage: %s PROPNAME [WC-PATH]" % (sys.argv[0])
print
print "List the set of paths in working copy WC-PATH ('.' by default)"
print "which contain the property name PROPNAME."
print
sys.exit(1)
prop_name = sys.argv[1]
wc_path = ''
if argc == 3:
wc_path = sys.argv[2]
if wc_path[-1] == '/' or wc_path[-1] == '\\':
wc_path = wc_path[:-1]
core.run_app(find_props, prop_name, wc_path)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by "C. Michael Pilato" <cm...@collab.net>.
Ron Bieber <ro...@bieberlabs.com> writes:
> I'd be glad to give you a wish list.
[wonderful feedback, though not necessary news to us, removed]
> 5. I'm not sure what this would be called, but it would be very useful
> for us to be able to query a list of files/revisions that have a
> property set to a certain value. For example, "give me all files where
> prop:defectnumber is 100". I know this type of functionality was
> discussed briefly in relation to tagging but I would use it in a
> completely different way so this implementation would have to be
> general.
Ah, I think I must have missed this suggestion in the past. I can
certainly see the utility of such a feature. Do you envision this
being something more than you can already do with shell tools? Want
me to write you a Python-bindings-using script to do this for you?
:-)
> I hope this helps. Once again, thanks for a great product.
Ron, thank *you* for taking the time to give useful feedback (pros
*and* cons).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Ron Bieber <ro...@bieberlabs.com>.
I'd be glad to give you a wish list.
1. Clearer error messaging when things happen like trying to merge a
non existent revision of a file. The current messaging isn't clear and
people get confused.
2. Repeated Merging Support - We currently use branching per activity,
and also "per release". We use our trunk as the "development", or
"unstable" branch, and then when we are ready to go to QA, we branch and
continue development on the release branch until production (this is the
same model you guys use I think). Once a build goes to production this
branch becomes our production support branch. Given this model,
repeated merging is a big deal for us as our merging from the "release
branch" is still done en masse rather than "per change". I plan on
changing this part of our model at some time in the future, however this
will be a big deal for people as we try to evangelize Subversion outside
of my group.
3. File Locking - We have one documentation CVS repository containing
Word documents and diagrams that we have not converted because of the
lack of locking support. Once we have locking we will be a 100%
Subversion shop. In addition, we have certain artifacts that we
publish per build that we currently publish by having a samba share to a
directory on our internal web servers. The ideal situation for this
scenario would be to set up a "web folder" so that our users could
upload files and they would be versioned "invisibly". Currently we
have no version control for these artifacts, and I do not want to teach
my business users to use source control. Full WebDAV autoversioning
would be huge win for us in this scenario. My understanding from
reading the book is that locking support is one of the reasons this
doesn't work.
4. Repository Replication - The svnadmin dump --incremental was a good
step towards this, and this is what I am using to replicate one of our
external repositories to our internal systems, however, I would love to
see real time replication. One of the things we are looking at is to
use SVN in some capacity for content management. With this goal
(actually, just sourcing your code falls under this category), failover
is very important, hence replication is a "must have". If we could
have a relational backend it would be that much better.
5. I'm not sure what this would be called, but it would be very useful
for us to be able to query a list of files/revisions that have a
property set to a certain value. For example, "give me all files where
prop:defectnumber is 100". I know this type of functionality was
discussed briefly in relation to tagging but I would use it in a
completely different way so this implementation would have to be
general.
6. More detailed API documentation. Currently I do not have the time
(nor does my staff) to dig around the code or current API docs. In
addition to using CruiseControl, we have wrapped our build process with
a lot of automation to enfoce the process. Most of this is now using
Python and the SVN command line, however we have a lot of Java code
running in Tomcat to help us administer the source base. A chapter in
the book with detailed documentation on using the SVN API would be great
(something like a cookbook with common things you would do to copy, co,
access properties, etc from C / Python / Java, etc).
7. Finally, more efficient workarea metadata management. Currently
under operating systems like Solaris, checkout times are very slow due
to the amount of small files that are copied / created / updated during
the checkout or update process (and the number of stat calls that are
performed). We currently have to use asynchronous file I/O under
these environments (for workareas, NOT THE REPOSITORY) with a very
aggressive backup strategy to ensure performance for the teams in this
environment. Figuring out a way to optimize this aspect of the product
would be a big win.
I hope this helps. Once again, thanks for a great product.
-- Ron
On Fri, 2004-07-23 at 09:56, C. Michael Pilato wrote:
> Ron Bieber <ro...@bieberlabs.com> writes:
>
> > As a manager, converting to Subversion was one of the best decisions I
> > have made thus far that had a such a direct and highly visible impact on
> > the productivity of my team.
> >
> > I hope this helps you make your case for Subversion. My personal
> > opinion is that no one should even consider CVS at this point in time.
> > Subversion is a great product and the support you get just on the
> > mailing lists alone (from the development team no less!) is second to
> > none.
>
> Wow. I think I might cry. That was not only a pleasant read, but it
> was quite encouraging.
>
> So -- because, as a developer of Subversion, I want to know -- could
> you list your top few complaints/wishlist items for Subversion?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Alan Jay Weiner <al...@ajw.com>.
>So -- because, as a developer of Subversion, I want to know -- could
>you list your top few complaints/wishlist items for Subversion?
The top of my list is to handle SourceSafe-like "shared" files. I have a bunch
of files that I commonly use in projects, and I don't want to have to share
*all* of them every time; i.e., I don't want to share the whole directory; just
individual files.
I'd be satisfied if I could put a filename onto svn:externals, if I could get
several files from different places into the same directory. It'd be good if I
could make the target directory '.' also, so I could have something like:
$ svn propget svn:externals srcs_common
. svn://localhost/common/trunk/hdrs/header.h
. svn://localhost/proj1/trunk/src1/file1.c
. svn://localhost/proj1/trunk/src1/file2.c
Other than this, it's been more of a difference in ways of thinking - I can do
most of what I want, although it's easier to change the way I think. (for
example, individual file timestamps aren't maintained)
- Al -
--
-- Alan Weiner -- alan@ajw.com -- http://www.ajw.com
Palm OS Certified Developer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Chris Wein <cw...@mobilygen.com>.
I also have had a very positive experience moving from CVS to Subversion
in a commercial setting. We are a small-ish silicon valley startup that
used to have everything in CVS. Shortly after I joined as s/w manager I
switched the s/w team to SVN (0.37) with excellent results. We have had
zero loss of data, zero down time, with effective branching, easy
repository restructuring and constant time tags as our big positives.
The entire company will be moving in the near-ish future based on our
pilot. And of course the support from this list is fantastic.
As for my wishlist, it is short - completely seamless and foolproof
tracking of merge history at the same level as the commercial tools. I
don't want to remember revision numbers, I just want to branch and merge
with the tool remembering common base versions etc. This is really the
only thing I miss about ClearCase.
Chris
On Fri, 2004-07-23 at 07:56, C. Michael Pilato wrote:
> Ron Bieber <ro...@bieberlabs.com> writes:
>
> > As a manager, converting to Subversion was one of the best decisions I
> > have made thus far that had a such a direct and highly visible impact on
> > the productivity of my team.
> >
> > I hope this helps you make your case for Subversion. My personal
> > opinion is that no one should even consider CVS at this point in time.
> > Subversion is a great product and the support you get just on the
> > mailing lists alone (from the development team no less!) is second to
> > none.
>
> Wow. I think I might cry. That was not only a pleasant read, but it
> was quite encouraging.
>
> So -- because, as a developer of Subversion, I want to know -- could
> you list your top few complaints/wishlist items for Subversion?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
--
Chris Wein
Software Manager
Mobilygen Corp.
E-Mail : cwein@mobilygen.com
Phone : 408-869-4035
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by "C. Michael Pilato" <cm...@collab.net>.
Ron Bieber <ro...@bieberlabs.com> writes:
> As a manager, converting to Subversion was one of the best decisions I
> have made thus far that had a such a direct and highly visible impact on
> the productivity of my team.
>
> I hope this helps you make your case for Subversion. My personal
> opinion is that no one should even consider CVS at this point in time.
> Subversion is a great product and the support you get just on the
> mailing lists alone (from the development team no less!) is second to
> none.
Wow. I think I might cry. That was not only a pleasant read, but it
was quite encouraging.
So -- because, as a developer of Subversion, I want to know -- could
you list your top few complaints/wishlist items for Subversion?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Ron Bieber <ro...@bieberlabs.com>.
Darren,
I currently manage a group of about 20 developers for a Fortune 500
company. We used CVS from January of 2001 until May of 2004 when we
converted all of our repositories over to Subversion.
The advantages we received from Subversion are immense. Before our
conversion to CVS from VSS, we had two full time employees managing our
production builds. Upon conversion to CVS we cut that resource count
down to one. This resource handled all branching and merging
activities, reporting activities, and manipulation of the CVS repository
to move files while retaining history. The CVS branching and merging
was just too cryptic (and took too long) for anyone to want to learn
it. We had two CVS "experts" in house which included me and one of my
direct reports. We were constantly called in to resolve issues. I
myself spent a ton of time managing the support of the CVS repositories.
After running across Subversion by chance in May of 2003, I started
piloting it at home. As I used it more, I became convinced that this
was a tool that my team needed in order to increase our productivity.
After using it for a while, I was able to come up with some specific
areas that justified our conversion to Subversion in order to maximize
our productivity and code quality:
1. Atomic commits - The lack of atomicity in commits was a huge problem
for us with CVS. Subversion gives us the confidence that when we
commit, everything went into the repository.
2. The ability to back out changes before going to production - using an
activity branching model, we can allow developers to branch per activity
and only merge to the main source base after code reviews have been
performed. If there are problems, we have one revision we can back out
that includes the full changeset for that change. While the repository
level revisioning was a shift for my developers to make that didn't
happen immediately, it begins to make sense when an activity had to be
removed from the build. In CVS we had to go through each file looking
for revisions that were effected by a change. Subversion now manages
this for us.
3. Decreased build time. We run CruiseControl, and the checkout times
we were experiencing with CVS, along with our requirement to tag of our
source base after each build caused our automated build cycle to take an
inordinate amount of time. With the restriction that all production
changes MUST go through the build, this made emergency situations very
stressful. The cheap copy functionality of Subversion decreased the
time it took to get a change into source control, through the build
system, and into deployment packages by 80%, greatly increasing our
response time.
4. Directory Versioning - this was a big deal that caused us to
actually evaluate Clearcase at one point. The CVS Attic was killing us
in checkout time and build time with the velocity of change we were
making to the source base. When checkout times got too slow, we would
have to wipe out the attic, effectively wiping out the history of our
source base. With Subversion, we can remove something from the
repository and not suffer performance penalties later (and still be able
to get the deleted contents back).
5. Simpler (and faster) branching - we no longer have a full time FTE
managing branches. We are now cycling this activity through the
group. Each developer can perform this activity, because it is now
part of his daily work.
As a manager, converting to Subversion was one of the best decisions I
have made thus far that had a such a direct and highly visible impact on
the productivity of my team.
I hope this helps you make your case for Subversion. My personal
opinion is that no one should even consider CVS at this point in time.
Subversion is a great product and the support you get just on the
mailing lists alone (from the development team no less!) is second to
none.
-- Ron
On Wed, 2004-07-21 at 09:48, Darren_Enns@cwb.ca wrote:
> Hello, I am new to this list. I have been participating in a 'proof
> of concept' project to implement Subversion into our company's
> computer environment.
>
> Everything is going fine, and everyone involved is very impressed with
> Subversion, except that we have hit a 'snag' in our plans -- the
> 'conservative' nature of our company will probably refuse the move to
> Subversion -- and pick 'CVS' instead -- since we don't want to be the
> 'first guys on the block' that use Subversion for mission-critical
> non-open-source project development.
>
> I have till this Friday to look for evidence that there are
> 'commercial' users of Subversion that are using it for
> 'mission-critical' development and are happy with it. The
> 'testimonials' page on the Subversion website contains lots of good
> 'open source' users, but I need testimonials from 'commercial' users.
>
> If you think you can help me, please let me know ASAP! I am
> desperate! :)
>
> Thanks!
>
> Dare
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Mark Bohlman <mb...@tcicredit.com>.
Ben Collins-Sussman wrote:
> On Wed, 2004-07-21 at 11:00, Eric Gillespie wrote:
>
>>Darren_Enns@cwb.ca writes:
>>
>>
>>>I have till this Friday to look for evidence that there are
>>>'commercial' users of Subversion that are using it for
>>>'mission-critical' development and are happy with it. The
>>>'testimonials' page on the Subversion website contains lots of
>>>good 'open source' users, but I need testimonials from
>>>'commercial' users.
>>
>>Two of the testimonials are commercial use: Conectiva and
>>Absolute Systems. We haven't submitted a testimonial (yet), but
>>we are using Subversion extensively at Lexmark, with large and
>>small repositories, totalling about 1500 revisions per month.
>
>
> See the testimonials page:
>
> http://subversion.tigris.org/propaganda.html
Being very much in the commercial realm:
Teledata Communications has been using Subversion for storing all of the
source code on all our software products for the past year (since
version 0.24). I have been very happy with the overall results and they
way that developer impacts are minimal. We have not lost a single byte
of code nor had any significant issues with using Subversion since the
beginning. I attribute part of the productivity gains we have see in
the past year to the move away from our prior system with locking (and
the corresponding messages back and for to have something 'unlocked').
We continued to expand the use of the product to all groups in the company.
Mark Bohlman
Software Development Manager
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Ben Collins-Sussman <su...@collab.net>.
On Wed, 2004-07-21 at 11:00, Eric Gillespie wrote:
> Darren_Enns@cwb.ca writes:
>
> > I have till this Friday to look for evidence that there are
> > 'commercial' users of Subversion that are using it for
> > 'mission-critical' development and are happy with it. The
> > 'testimonials' page on the Subversion website contains lots of
> > good 'open source' users, but I need testimonials from
> > 'commercial' users.
>
> Two of the testimonials are commercial use: Conectiva and
> Absolute Systems. We haven't submitted a testimonial (yet), but
> we are using Subversion extensively at Lexmark, with large and
> small repositories, totalling about 1500 revisions per month.
See the testimonials page:
http://subversion.tigris.org/propaganda.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Eric Gillespie <ep...@pretzelnet.org>.
Darren_Enns@cwb.ca writes:
> I have till this Friday to look for evidence that there are
> 'commercial' users of Subversion that are using it for
> 'mission-critical' development and are happy with it. The
> 'testimonials' page on the Subversion website contains lots of
> good 'open source' users, but I need testimonials from
> 'commercial' users.
Two of the testimonials are commercial use: Conectiva and
Absolute Systems. We haven't submitted a testimonial (yet), but
we are using Subversion extensively at Lexmark, with large and
small repositories, totalling about 1500 revisions per month.
--
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by John Szakmeister <jo...@szakmeister.net>.
I work for a government contracting facility. We develop everything from
hardware, to full-fledged software applications, all of which supports
mission-critical activities. We're currently using it on one of our most
productive teams, and houses about 3 years worth of work (for about 14
developers). We started off with CVS, and found that the customer was
constantly coming back with request for features and upgrades. Our small
test projects would turn into fully-funded applications, and as such, we
had to restructure them. It was just too painful with CVS, and we
decided to look for something better.
We found Subversion when it was at version 0.17. We started with just a
few developers using it, and then migrated our other developers over
time. I can say without question that it has been one of the best
decisions that we've made. Subversion works better than CVS ever did.
We can detect corruption before it gets to be a problem, we get atomic
commits, and directory versioning. All of which has made our development
process and our ability to adapt to the customers' ever-changing
requirements that much easier. Plus, it natively supports both the
Windows and Linux platforms (versus the mixing of CVS and CVSNT that we
had before), which is our primary development platforms. We've never
lost any data, and our developers have found it to be a very intuitive
tool. Subversion has been rock-solid in our environment, and very much
complements our software engineering practices. I can't speak highly
enough of it.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Commercial Users of Subversion: LET ME KNOW
Posted by Robert Zeh <rz...@efs-us.com>.
I manage a 13 member application development group for a trading firm.
There are about 9 other developers outside the group, and some others,
so we have about 20 people using our subversion repository.
For the past 10 years we used SCCS. It was very frustrating --- files
could not be renamed or moved, developers would forget about locks they
had acquired, and remote development was next to impossible. SCCS also
made our limited Windows development painful (we are a Unix shop).
Since we switched to subversion things have been much better. Our
entire history was transported into our Subversion repository, so none
of our history was lost. I wrote a Python script to transform it
directly from SCCS to Subversion, and it was painless.
Conflicts have been very rare. The ability to easily branch has been
very useful; developers can make commits to branches without breaking
other people's code. It's easier to see what people are working on as
the commits hit our internal commit mailing list. Since we tag each
release, we're able to determine which source code contributed to a
release. TortiseSVN makes Windows development easy (no more ftping
files over, or trying to build on a remotely mounted samba drive).
Robert Zeh
Manager, Application Development
Error Free Software
Darren_Enns@cwb.ca wrote:
>
> Hello, I am new to this list. I have been participating in a 'proof
> of concept' project to implement Subversion into our company's
> computer environment.
>
> Everything is going fine, and everyone involved is very impressed with
> Subversion, except that we have hit a 'snag' in our plans -- the
> 'conservative' nature of our company will probably refuse the move to
> Subversion -- and pick 'CVS' instead -- since we don't want to be the
> 'first guys on the block' that use Subversion for mission-critical
> non-open-source project development.
>
> I have till this Friday to look for evidence that there are
> 'commercial' users of Subversion that are using it for
> 'mission-critical' development and are happy with it. The
> 'testimonials' page on the Subversion website contains lots of good
> 'open source' users, but I need testimonials from 'commercial' users.
>
> If you think you can help me, please let me know ASAP! I am
> desperate! :)
>
> Thanks!
>
> Dare
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org