Title: Migrate EpiDoc Repository to Subversion
This is an EpiDoc UserStory
- Originator(s): TomElliott
- Associated Bug/Feature Request(s):
- Markup List subject line(s)
Summary
- Subversion (SVN) is the next-generation replacement for the Concurrent Versioning System (CVS).
Examples
Dependencies and rules
- Sourceforge has an automated migration tool, but it will require supervision and testing
- EpiDoc developers will be required to use different (easier-to-use) client software
- Web site will need updates to indicate new details
Questions
- Repository will not be available during migration (how long?)
- What are exact steps?
Acceptance Tests
- Is there a way to compare a CVS-origin sandbox to a SVN-origin sandbox to make sure nothing got borked in the migration?