Version 2 (modified by dukeleto, 12 years ago)


This page exists to document what needs to happen before Parrot's developers will feel confident about switching version control from Subversion to Git.


  • Backwards-compatibility of svn revision numbers. We aren't patient enough to change all references in Parrot and Trac to svn revisions, so there has to be a way to figure out what changes a svn revision refers to. This can be done by maintaining a read-only version of the svn repository.
    • When importing a SVN repo into Git, we have the choice of adding markers to each commit which reference the original SVN revision. It sounds like we want this.
  • Trac integration - We aren't switching away from Trac, so we need to be sure that there's a *mature* Trac plugin that can work with Git, either directly or via a third-party host like  GitHub. This needs to be researched carefully since poor or immature Trac integration could be a significant impediment to Parrot's progress.