www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11794) Migrate Qpid C++ to Git
Date Tue, 05 Jul 2016 21:41:11 GMT

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

Robbie Gemmell commented on INFRA-11794:

The new repository appears to be good to go:

The history all looks to be there, and the current HEAD contents are binary identical to a
current checkout of the matching subdir of the svn repo, with one trivial exception we can
ignore [1].

Some things to finish off the transition spring to mind. Happy to raise additional JIRAs for
any of these if needed:

- Can we have git.apache.org and GitHub mirrors set up for the new repo?
- Can we have the GitHub integration features enabled, with mails going to the dev@qpid.apache.org
- Can we have gitsvn2jira enabled, configured for matching QPID-<foo> JIRA keys, and
mailing the dev@qpid.apache.org list.
- Can we have ReviewBoard enabled for the repo?


[1] A handful of empty example dirs for qpid-cpp (such as qpid/cpp/bindings/qpid/dotnet/examples/msvc9/csharp.example.server/
and some siblings) didnt make the transition, since git doesnt version directories.

Checking with [~chug] he doesnt see an issue with that, and upon further checking he actually
deleted the files in the dirs nearing a couple years ago: http://svn.apache.org/viewvc?view=revision&revision=1624604.
There doesnt apear to be any issue, but if there is it has nothing to do with the transition
and we can address it separately.

> Migrate Qpid C++ to Git
> -----------------------
>                 Key: INFRA-11794
>                 URL: https://issues.apache.org/jira/browse/INFRA-11794
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git, Subversion
>            Reporter: Justin Ross
>            Assignee: Chris Lambertus
> The Apache Qpid project would like to request migration of the Qpid C++ code to a Git
repository.  This code was formerly one piece of a larger project, but it is now being split
out as standalone.
> A vote concerning this was made on the Qpid users list at [1], with the result available
at [2]. 
> The existing code is available in Subversion at: 
> http://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp
> The existing codebase is in use for other components as well, so if anything is made
read-only in the process, it should be only the tree under /asf/qpid/trunk/qpid/cpp.
> We'd like the primary branch under Git to be "master" (not "trunk").  We'd like the Git
repository name to be "qpid-cpp".
> 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. 
> [1] Vote: http://qpid.2158936.n2.nabble.com/VOTE-Migrate-Qpid-C-and-Qpid-Python-to-Git-tp7642642.html
> [2] Result: http://qpid.2158936.n2.nabble.com/RESULT-VOTE-Migrate-Qpid-C-and-Qpid-Python-to-Git-tt7643013.html
> [3] Commits list: commits@qpid.apache.org 
> [4] JIRA project: https://issues.apache.org/jira/browse/QPID 

This message was sent by Atlassian JIRA

View raw message