You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jeremy Thomerson (Created) (JIRA)" <ji...@apache.org> on 2011/12/10 02:24:43 UTC

[jira] [Created] (INFRA-4204) Migrate Apache Wicket to Git

Migrate Apache Wicket to Git
----------------------------

                 Key: INFRA-4204
                 URL: https://issues.apache.org/jira/browse/INFRA-4204
             Project: Infrastructure
          Issue Type: Task
      Security Level: public (Regular issues)
          Components: Git
            Reporter: Jeremy Thomerson
            Priority: Minor


The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:

Current location: https://svn.apache.org/repos/asf/wicket/
It's a pretty standard layout with trunk/tags/branches.  
The other directories in it are:
sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
releases: release branches
common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.

Apache User ID for infra volunteer: jrthomerson


--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Jeremy Thomerson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174143#comment-13174143 ] 

Jeremy Thomerson commented on INFRA-4204:
-----------------------------------------

Martin, I think it is planned: INFRA-4157
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Closed] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-4204.
------------------------------------

    
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174132#comment-13174132 ] 

Martin Grigorov commented on INFRA-4204:
----------------------------------------

Is it possible to add Git Commits plugin for Jira ?
Or this will confuse the SVN projects somehow ?
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Igor Vaynberg (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174203#comment-13174203 ] 

Igor Vaynberg commented on INFRA-4204:
--------------------------------------

hrm, even after `git symbolic-ref HEAD refs/heads/master`  some users are still seeing trunk as the default branch after a clone. i am guessing the way git repos are mirrored that command may need to be run on all servers. or the HEAD file edited in all the repos...
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Paul Joseph Davis (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173824#comment-13173824 ] 

Paul Joseph Davis commented on INFRA-4204:
------------------------------------------

Docs on getting started for committers can be found here:

http://git-wip-us.apache.org/#committers-getting-started
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "#asfinfra IRC Bot (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166810#comment-13166810 ] 

#asfinfra IRC Bot commented on INFRA-4204:
------------------------------------------

<danielsh> we need another volunteer who is a wicket committer

                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173814#comment-13173814 ] 

Joe Schaefer commented on INFRA-4204:
-------------------------------------

svn tree set read-only, git repo activated.  You will need to
work with Gavin on restoring buildbot to working condition.
Let us know what you'd like us to do with the remainder
of your svn tree.

                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Resolved] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved INFRA-4204.
----------------------------------

    Resolution: Fixed

The symbolic HEAD ref of the git-wip-us repository was still pointing to "refs/heads/trunk" (you can't remotely change the HEAD of a repository). During the initial clone of the repository, the git client reads the HEAD ref to see which branch the newly cloned repository should start following by default, which is why new clones of the wicket repository were still referencing the old trunk branch.

I fixed the HEAD ref on the server, which should resolve the last bit of this issue. Thus resolving as fixed.
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Igor Vaynberg (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175611#comment-13175611 ] 

Igor Vaynberg commented on INFRA-4204:
--------------------------------------

Gavin, please see my comment above about trunk branch still being the default HEAD on some servers...
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166746#comment-13166746 ] 

Joe Schaefer commented on INFRA-4204:
-------------------------------------

jrthomerson added to infra- welcome aboard.  Please visit https://git-wip-us.apache.org/
for details on how to access the infra git repo.
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Igor Vaynberg (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173844#comment-13173844 ] 

Igor Vaynberg commented on INFRA-4204:
--------------------------------------

renamed trunk to master

{code}
git branch -m trunk master
git push origin master
git symbolic-ref HEAD refs/heads/master
{code}
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Gavin (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175637#comment-13175637 ] 

Gavin commented on INFRA-4204:
------------------------------

Saw that, what are 'some servers' , please explain what and where these are.
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "#asfinfra IRC Bot (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166761#comment-13166761 ] 

#asfinfra IRC Bot commented on INFRA-4204:
------------------------------------------

<joes4> its in https://git-wip-us.apache.org/repos/infra/asfgit-admin.git

                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166853#comment-13166853 ] 

Martin Grigorov commented on INFRA-4204:
----------------------------------------

I'm in: mgrigorov.
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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

        

[jira] [Commented] (INFRA-4204) Migrate Apache Wicket to Git

Posted by "Gavin (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175608#comment-13175608 ] 

Gavin commented on INFRA-4204:
------------------------------

Is there anything else to do on this ticket?
                
> Migrate Apache Wicket to Git
> ----------------------------
>
>                 Key: INFRA-4204
>                 URL: https://issues.apache.org/jira/browse/INFRA-4204
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jeremy Thomerson
>            Priority: Minor
>
> The Wicket project would like to be migrated to the ASF git hosting infrastructure.  Here are some additional details:
> Current location: https://svn.apache.org/repos/asf/wicket/
> It's a pretty standard layout with trunk/tags/branches.  
> The other directories in it are:
> sandbox: branches individual developers used to test stuff out.  Hasn't been committed to in nearly two years.
> releases: release branches
> common: really this is a whole separate source tree of our common files - public keys, site skin, etc....  I'm not sure what the currently-recommended solution for dealing with this is, but I'd see it either staying in SVN or else being a separate git repo.
> Apache User ID for infra volunteer: jrthomerson

--
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