Subversion has rapidly become the version control standard and it is rapidly replacing open source and commercial solutions around the world.
Subversion enables globally distributed software development teams to efficiently version and share source code. The open source Subversion project was started in early 2000 by CollabNet, the primary corporate sponsor of Subversion.

Key Capabilities:
- Versioned directories
- Atomic commits
- Efficient handling of binary files
- Quick branching and tagging
- Directory and file meta data
- Natively client-server
- Minimal server and network requirements
- Low admin overhead
- Good security

more at: http://subversion.tigris.org/

Read Submerged, a blog about Subversion at http://blogs.open.collab.net/svn

Journal Entries

Avatar

Fixed up some positions for the pulseaudio project. They moved from subversion to git and the aliases weren't mapped properly. jason — 2 months ago tags: PulseAudio,Subversion,Git

Avatar

tweaking my php code to make better use of ffmpeg and using subversion to make sure I have the newest version of ffmpeg jhalls — 2 months ago tags: PHP,FFmpeg,Subversion,FFmpeg

See All Journal Entries


Ratings & Reviews

Community Rating
4.3/5.0

Based on 686 user ratings.

Your Rating

Click to rate this project.

about 1 year ago Avatar
Why are you still using CVS?

    by GrumpyOldMan

Subversion is what CVS should have been. It's no mystery that projects are moving en masse from CVS to Subversion.

Subversion follows the same client/server model as CVS, but is a strictly better implementation. Subversion's command line tools will feel familiar to anyone comfortable with CVS, and most of the clever accessories like Tortoise and online code browers are available for Subversion. It's worth making the switch for the ... [More] elegant, efficient branching and tagging alone.

All this being said, I think the client/server source control model is on the way out. I highly recommend taking a look at Git or Darcs, which use a decentralized model that doesn't require a central server. [Less]

23 of 33 users found the following review helpful. Was this review helpful to you? |

8 months ago Avatar
Sure it's not edgy, but it's not junk either

    by Rob Heittman

Subversion was chartered specifically to create a drop-in replacement for CVS -- something that worked similarly, but was friendly to the HTTP infrastructure and addressed some key limitations like the ability to version the directory tree structure. It's done what it set out to do, it's reached a stage of maturity and ubiquity, and I've found it to work reliably and well.

Of course most of the interesting work on source control is now ... [More] being done elsewhere, in projects that intentionally aren't carrying any baggage from CVS and before.

I'm sure at some point in the not too distant future, my team will be moving to something like git, because that's indeed the next evolutionary step. Who wouldn't want smaller working copies, faster updates, and better, legacy-free approaches to merge drudgery, etc?

But more integrations and tool support are needed -- as well as working connectors for services like Ohloh, and project hosting at places like Google Code, Sourceforge, etc, before I can fully make the leap to a late-model revision control platform, instead of just dabbling. I'm doing my little bit to push that forward, working on a git integration with our content management platform and bugging my vendors for git support.

Anyway, Subversion has been a good friend at work for about 5 years, and will be for a while longer before we move on ... and I don't feel any need whatsoever to beat it up for not being designed from scratch in the 21st century. We'll move on someday, but we won't go away mad.
[Less]

13 of 14 users found the following review helpful. Was this review helpful to you? |

Links

7 links submitted so far. Submit your own links.

News

Edit RSS feeds.

    Gurtle

    TortoiseSVN 1.5 allows using plug-ins for specific issue trackers.

    read more

    ÈGhDp3sug%

    %%LM30nmDx%%

    TortoiseSVN 1.5.3 released

    TortoiseSVN 1.5.3 has been released, still linked against Subversion
    1.5.2.

    This is a bugfix/maintenance release only. No new features were added
    since 1.5.2.

    You can get it from our download page.

    Steering Subversion

    When the Subversion project first launched, it was blessed to have
    something that many much older projects still lack: a clear direction. It
    would have been easy — and certainly the temptation existed — to try to
    make Subversion all ... [More] things to all people. Why settle for "a compelling
    replacement for CVS" (which was the goal at the time) when we could shoot
    for "best-of-class version control"? "Next-generation SCM solution"? "All
    that and a bag of chips?" Here's why: so the developers could get
    anything accomplished at all. It's as the old Proverb says (though
    admittedly in a different context), "Where there is no vision, the people
    perish." Without a single, clear sense of direction, you're left either
    meandering about with no sense of direction at all or (worse) stalemated
    by N senses of opposing directions. So how do the leaders of an open
    source software project choose a direction and set goals? And where do
    you, the reader, fit into all of this? Read on.

    As I said before, Subversion originally had a vision of being a
    compelling replacement for CVS and nothing more. And that's exactly what
    Subversion 1.0 was. But where do you go when you've been operating with a
    single goal in mind and then you reach that goal? Well, in Subversion's
    case, the 1.0 target was never even considered as the last station on the
    line. The developers always knew we wanted to push well past being a mere
    replacement for CVS. Really, the sky was the limit on where we could have
    driven Subversion. The project had already amassed a feature wishlist
    from its own developers anxious to scratch their version control itches
    and from early-adopting Subversion users. And new ideas were popping up
    daily. So Subversion started picking away at those features which seemed
    to its developers to provide the most bang for the buck.

    Meanwhile, our little software tool was finding its way into the hands of
    a different class of user than we tended to interact with in the open
    source arena. CollabNet packaged Subversion 1.0 into its CollabNet
    Enterprise Edition software, and suddenly Subversion was being adopted
    officially by segments of some rather large corporate enterprises.
    Instead of being used to replace only CVS, Subversion was displacing the
    likes of Microsoft's Visual SourceSafe, Perforce, and in some cases,
    threatening even heavyweights like IBM Rational's ClearCase. Those kinds
    of installations brought with them a whole new class of feature and
    enhancement requests.

    CollabNet — as the vendor which founded Subversion, remained the greatest
    source of funding for its development, and delivered Subversion to the
    Enterprise — recognizes the value of clear goals. And it also recognizes
    that one of the key benefits it can provide to the Subversion open source
    community is the valuable feedback of its customers, which tend to shy
    away from public discussion forums. CollabNet has over time helped the
    Subversion developers to get a better sense of what its customers are
    looking for in an enterprise-class version control system, mostly notably
    with its activities around the requirements gathering, design,
    development, and beta testing program for the merge tracking feature
    recently released in Subversion 1.5.

    Those of you familiar with the Subversion 1.5 release and the merge
    tracking development process know that this was a beast of a feature.
    Hard to define, hard to design, and hard to implement, this flagship
    feature of the 1.5 release was somewhat all-consuming at times. And the
    feature still isn't completely finished. But as the Subversion developers
    come up for air in the wake of the 1.5 release, we find ourselves at that
    familiar place again — the place where another major milestone is behind
    us and we're looking forward to the future. As always, there's no
    shortage of wishlist items to consider, and development is already well
    under way on some of those things. But we continue to learn more about
    our users, about their needs, about ourselves, and about what Subversion
    can and cannot do today. And that's where you fit in.

    While it is true that sometimes programmers wish they could turn off all
    the noise around them so they can focus on the task at hand, Subversion's
    developers have always understood that there's usually some signal in
    that noise, a thread of meaningful input that's worth attending to. Your
    participation in the Subversion development community is vital to the
    continued success of this software. We need and want to hear what you
    have to say about Subversion and how it does or doesn't meet your version
    control needs.

    To that end, allow me to make you aware of a special opportunity you will
    have to do exactly this. The second annual SubConf Subversion user
    conference is being held October 14-16, 2008, in Munich. CollabNet has
    worked with the conference organizers to arrange for a special roundtable
    discussion session (to be held Tuesday evening, the 14th) in which you,
    the Subversion user, can meet some of the Subversion committers in person
    and share your experiences with us. This is not a lecture-style session
    where we do all the talking. We want to listen. This is a great way for
    those of you averse to communicating in open source forums to make your
    opinions and desires known. I'll be chairing the roundtable session, and
    many of my colleagues will be present, too. We hope to see you there!

    For more information on the SubConf conference, visit
    http://www.subconf.conf/ [German].
    For information about the SubConf Subversion Roundtable, visit
    http://www.subconf.com/roundtable/ [German]. [Less]

    Steering Subversion

Read all Subversion articles…


Who uses Subversion?

Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32

Who contributes to Subversion?

Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32 Anon32
I'm a contributor

Where in the world?




People who use Subversion also use:


Project Cost

This calculator estimates how much it would cost to hire a team to write this project from scratch. More »
Include
Codebase 369,306
Effort (est.) 97 Person Years
Avg. Salary $ year
$ 5,347,287