You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "David Nalley (JIRA)" <ji...@apache.org> on 2013/05/02 06:08:15 UTC

[jira] [Updated] (INFRA-6197) Migrate Apache Camel from svn to git

     [ https://issues.apache.org/jira/browse/INFRA-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Nalley updated INFRA-6197:
--------------------------------

    Status: Waiting for user  (was: Waiting for Infra)

Hadrian: 

Your SVN tree is now RO.
Your git repo is here: https://git-wip-us.apache.org/repos/asf/camel.git 
It also is currently RO. 

Please have the PMC audit the git repo for completeness - and if acceptable (or not) please update this ticket and I'll make it writable. (along with camel/site in svn.)

                
> Migrate Apache Camel from svn to git
> ------------------------------------
>
>                 Key: INFRA-6197
>                 URL: https://issues.apache.org/jira/browse/INFRA-6197
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Hadrian Zbarcea
>            Assignee: David Nalley
>
> The Apache Camel PMC would like to ask infra to pretty please migrate the codebase from svn to git. The majority of the developers already use the git mirror (for a long time). This was discussed on the dev@ list [1] and unanimously accepted (if a formal PMC vote is needed please let us know).
> We would need to move the trunk, branches and tags.
> The website [2] would need to stay in svn and stay writable, as it contains the public site.
> The other directories (ide, m2-repo, scripts, sandbox) do not need to be migrated (then can stay r/o in svn).
> [1] http://mail-archives.apache.org/mod_mbox/camel-dev/201303.mbox/%3C51535002.3070806%40gmail.com%3E
> [2] https://svn.apache.org/repos/asf/camel/website/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira