Upload
wandisco-plc
View
2.403
Download
2
Embed Size (px)
Citation preview
Why Subversion?
Hyrum WrightPresident of the Subversion Corporation
Director of Open Source at WANdisco
“Subversion is the indisputable
leader on standalone SCM. Simple
and sufficient SCM capabilities, an
open source license, and a vibrant
ecosystem make Subversion the
Leader in the standalone SCM
market. At this point, Subversion
is no longer some-thing that's on
the horizon: it really has arrived,
and it has been embraced by
application development
organizations of all shapes and
sizes.”
—Carey SchwaberForrester Research, Inc.
Copyright © 2010 WANdisco, Inc. All rights reserved. 3
Why Subversion
► Demonstrated maturity
► Increased corporate adoption (Intel, HP, Cisco, Oracle, World Bank, DHL, etc…)
► Replacing in-house, ad-hoc and commercial SCM implementations
► Standardizes an enterprise’s toolset
► Low cost coupled with easy administration
► Numerous clients and IDE integrations due to open APIs, open source.
► Wide industry support
Copyright © 2010 WANdisco, Inc. All rights reserved. 4
Why Subversion
Commercial SCM products
Commercial Java IDE Solutions
Solaris, AIX, HP-UX, Irix, DEC Unix, etc.
Copyright © 2010 WANdisco, Inc. All rights reserved. 5
Why Subversion
► Subversion is a commercial quality version control system from an open-source team
► Designed with database concepts to protect code• Atomic Commits• Client side journaling for file updates
► Provides advanced SCM capabilities• Directory/file renaming and versioning• Automatic merge/merge tracking
► Open, extensible architecture• Additional capability provided through open source plug-ins• Integrations with leading issue tracking solutions
– JIRA, Trac, Bugzilla, etc.• A wide variety of Subversion clients available
– Web, Eclipse, Visual Studio, Windows Explorer, WebDAV aware
Copyright © 2010 WANdisco, Inc. All rights reserved. 6
Why Subversion► Features introduced in SVN 1.5
• Built-in merge tracking• Interactive conflict resolution• FSFS sharding (file management in subdirectories)• Sparse checkouts
► Features introduced in SVN 1.6• Many new features, mostly client side• New repository format with file i/o, caching optimizations• Working copy format update• Merge tracking performance improvements• Client side authentication enhancements; relative URLs
► Looking ahead to SVN 1.7• Working copy update (moving from flat to SQLite files)• New HTTP v2 protocol
► Future directions?