User:Cmray4: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 2: | Line 2: | ||
SVN or Apache Sub-Versioning (formerly Sub-Versioning), was developed as a replacement to CVS (Concurrent Versioning System) due to the issues it faced. Collabnet Inc., a company that specializes in lifecycle management software, decided not to amend CVS, but develop a new concept of versioning control, omitting issues and adding features not available within CVS. With the assistance of Karl Fogel, co-author of ''Open Source Development With CVS'', and Jim Blandy, SVN came into being and distributed as an open source tool. | SVN or Apache Sub-Versioning (formerly Sub-Versioning), was developed as a replacement to CVS (Concurrent Versioning System) due to the issues it faced. Collabnet Inc., a company that specializes in lifecycle management software, decided not to amend CVS, but develop a new concept of versioning control, omitting issues and adding features not available within CVS. With the assistance of Karl Fogel, co-author of ''Open Source Development With CVS'', and Jim Blandy, SVN came into being and distributed as an open source tool. | ||
== Issues Regarding CVS == | |||
== Development of SVN == | == Development of SVN == | ||
Revision as of 04:32, 2 September 2010
Summary
SVN or Apache Sub-Versioning (formerly Sub-Versioning), was developed as a replacement to CVS (Concurrent Versioning System) due to the issues it faced. Collabnet Inc., a company that specializes in lifecycle management software, decided not to amend CVS, but develop a new concept of versioning control, omitting issues and adding features not available within CVS. With the assistance of Karl Fogel, co-author of Open Source Development With CVS, and Jim Blandy, SVN came into being and distributed as an open source tool.