Why Svn

  • 2,359 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,359
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
34
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Why Subversion? Hyrum Wright President of the Subversion Corporation Director of Open Source at WANdisco
  • 2. “ 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 Schwaber Forrester Research, Inc.
  • 3. Why Subversion
  • 4. Why Subversion
  • 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
  • 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?