www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-6197) Migrate Apache Camel from svn to git
Date Mon, 06 May 2013 15:32:16 GMT

    [ https://issues.apache.org/jira/browse/INFRA-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649801#comment-13649801

Hadrian Zbarcea commented on INFRA-6197:

David, awesome, thanks a a bunch! It looks ok to us, got confirmation from a few of the other
committers on the tread linked above. We believe everything is in order and you could go ahead
and make the repo writable. We'll take care of publishing the change and other necessary tasks.
You also did it fast and the timing was great as it created virtually no disruption for us.
Many thanks again!
> 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
> 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

View raw message