www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marios Andreou (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4220) Migrate Apache Deltacloud to git
Date Tue, 14 Feb 2012 14:04:59 GMT

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

Marios Andreou commented on INFRA-4220:

@Joe any ideas how we'd go about updating our public website? Previously we'd ssh into people.apache.org
and svn update our deltacloud directory. Is there a different process now that we're 'on git'?
> Migrate Apache Deltacloud to git
> --------------------------------
>                 Key: INFRA-4220
>                 URL: https://issues.apache.org/jira/browse/INFRA-4220
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: David Lutterkort
>            Assignee: Joe Schaefer
>            Priority: Minor
> The Deltacloud project would like to be migrated to the ASF git hosting infrastructure.
> The Deltacloud subversion repo is at https://svn.apache.org/repos/asf/deltacloud/ and
uses the standard trunk/tags/branches layout. If at all possible, we'd like the trunk to become
the master branch of the repo; for the svn tags, I'd love to recreate them as signed git tags,
signed with my GPG key. Any help you can provide me for that (e.g., git hashes corresponding
to the svn tags) would be much appreciated, but I can generate that myself.
> Besides trunk/tags/branches, the svn repo contains a file README at the toplevel; that
can either be deleted/dropped, or moved into the top level of the git repo (which should correspond
to https://svn.apache.org/repos/asf/deltacloud/trunk/)
> Apache user ID for helpers: I will be the point person (lutter), Marios Andreou (marios)
also wants to help out.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message