www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-12350) Finalize Migration of Apache Commons CSV to git
Date Fri, 29 Jul 2016 08:31:20 GMT
Benedikt Ritter created INFRA-12350:

             Summary: Finalize Migration of Apache Commons CSV to git
                 Key: INFRA-12350
                 URL: https://issues.apache.org/jira/browse/INFRA-12350
             Project: Infrastructure
          Issue Type: Bug
          Components: Git
            Reporter: Benedikt Ritter

This is a follow up to INFRA-12092. After the code of Apache Commons CSV has been migrated
to git, we need to archive the old SVN tree. What we would currently do for a component named
foo is:

- make https://svn.apache.org/repos/asf/commons/_moved_to_git writetable
- create https://svn.apache.org/repos/asf/commons/_moved_to_git/foo
move everything below https://svn.apache.org/repos/asf/commons/foo to https://svn.apache.org/repos/asf/commons/_moved_to_git/foo
- add a FooNowUsesGit.txt to https://svn.apache.org/repos/asf/commons/foo (for an example
see https://svn.apache.org/repos/asf/commons/proper/lang/LangNowUsesGit.txt )
- make https://svn.apache.org/repos/asf/commons/foo read-only
- make https://svn.apache.org/repos/asf/commons/_moved_to_git read-only

This would have to be done for Commons CSV. The old svn tree is at https://svn.apache.org/repos/asf/commons/proper/csv

In the past we did this with help by infra. Now I'm wondering whether is would be feasible
to grant some of the Apache Commons PMC members the karma to change the permissions of our
SVN tree so we can do this ourself in the future.

Thank you!

This message was sent by Atlassian JIRA

View raw message