You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Chris Colman (JIRA)" <ji...@apache.org> on 2014/11/17 11:19:34 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=14214484#comment-14214484 ]
Chris Colman edited comment on WICKET-5762 at 11/17/14 10:19 AM:
-----------------------------------------------------------------
No, by "go live" I meant deploy to the http://wicket.apache.org server.
Setting up these subtasks is for the purpose of finding the minimum set of 'blocking' issues/tasks that must be resolved before go live so that they can be assigned/tracked etc., Theoretically if we enumerate all the blocking issues and then resolve them in a timely manner we'll have a new wicket website that can go live soon - which, gauging from the response, is urgently needed.
was (Author: chrisc):
No, by "go live" I meant deploy to the http://wicket.apache.org server.
Setting up these subtasks is for the purpose of finding the minimum set of 'blocking' issues/tasks that must be resolved before go live so that they can be assigned/tracked etc., Theoretically if we enumerate all the blocking issues and then resolve then we'll have a new wicket website that can go live - which, gauging from the response, is urgently needed.
> 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)