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

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