You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/12/03 13:14:12 UTC
[jira] [Resolved] (WICKET-5762) Resolve issue of new site in Git vs
SVN
[ https://issues.apache.org/jira/browse/WICKET-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-5762.
-------------------------------------
Resolution: Done
I see nothing more to be discussed here.
The code of the new site is at https://github.com/bitstorm/wicket-site.
It "staging" deployment is at http://bitstorm.github.io/wicket-site/.
Once we decide it is good enough to replace the old one we should export the code and put it at https://svn.apache.org/repos/asf/wicket/common/site/trunk.
>From there on any work will be done in SVN.
I also don't like SVN but Apache infra team doesn't like Git that much :-/
> Resolve issue of new site in Git vs SVN
> ---------------------------------------
>
> Key: WICKET-5762
> URL: https://issues.apache.org/jira/browse/WICKET-5762
> Project: Wicket
> Issue Type: Sub-task
> Components: site
> Reporter: Chris Colman
> Priority: Minor
>
> Martijn's great looking new design is currently on Github yet Apache requires use of SVN. Do we create a Git <-> SVN bridge or switch to SVN?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)