www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8369) migrate Qpid JMS to Git
Date Sat, 20 Sep 2014 08:46:34 GMT

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

Daniel Gruno commented on INFRA-8369:
-------------------------------------

Hi Robbie,
I will walk Geoff through setting up svngit2jira for the new git repo :)
And you are correct, the git.a.o mirror needs to point at git-wip now, I will make sure that
happens as well

> migrate Qpid JMS to Git
> -----------------------
>
>                 Key: INFRA-8369
>                 URL: https://issues.apache.org/jira/browse/INFRA-8369
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git, Subversion
>            Reporter: Robbie Gemmell
>            Assignee: Geoffrey Corey
>
> The Apache Qpid project would like to request migration of the Qpid JMS code to a Git
repository.
> A vote concerning this was made on the users list at [1], with the result is available
at [2].
> The existing code is available in Subversion at:
> http://svn.apache.org/repos/asf/qpid/jms/
> The repo currently has commits emails sent to our commits list [3], and gitsvn2jira integration
enabled for its JIRA project [4]. We would like these features to to be similarly enabled
for the new Git repo.
> We currently have a git mirror of the existing repo at [5], which is in turn mirrored
to Github [6]. We would like the former updated to reflect the new Git repo.
> Any time suits to make the current repo read-only to do the migration.
> Finally, I beleive the typical migration process would normally leave the old repository
contents in place as read-only, is that correct? If so, would it be possible to instead remove
the old bits entirely once the transition is complete? This is a new codebase which is still
being built out and there are as yet no releases or branches/tags in the current repo, so
there would seem to be less reason anyone should use the old location in future to warrant
leaving it in place.
> Thanks,
> Robbie
> [1] Vote: http://mail-archives.apache.org/mod_mbox/qpid-users/201409.mbox/%3CCAFitrpTbcWx1gwnPVHKzxZ0SUW8_fXUgn4XFZtZ3Gqv1j9hebQ%40mail.gmail.com%3E
> [2] Result: http://mail-archives.apache.org/mod_mbox/qpid-users/201409.mbox/%3CCAFitrpSAcksk6afgPg0JkX1hLTsXQBMw10REnrDUDWAfbGU41A%40mail.gmail.com%3E
> [3] Commits list: commits@qpid.apache.org
> [4] JIRA project: https://issues.apache.org/jira/browse/QPIDJMS
> [5] Existing Git mirror: http://git.apache.org/qpid-jms.git
> [6] Github mirror: https://github.com/apache/qpid-jms



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message