www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5661) svnpubsub for Derby
Date Sun, 16 Dec 2012 11:36:12 GMT

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

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

<danielsh> If db.staging.apache.org has already been set up, all you need to do is set
up extpaths.txt to contain "derby" and then commit to https://svn.apache.org/repos/infra/websites/production/db/content/derby/

                
> svnpubsub for Derby
> -------------------
>
>                 Key: INFRA-5661
>                 URL: https://issues.apache.org/jira/browse/INFRA-5661
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: SvnPubSub
>            Reporter: Rick Hillegas
>
> The Derby subproject of the DB project is migrating to svnpubsub. This involved putting
our released user docs into the subversion repository which contains the rest of our website.
We have done that.
> At this time, we would like to ask the Infrastructure team to hook our website into the
svnpubsub machinery:
> o our public website lives at http://db.apache.org/derby/
> o our website's subversion repository lives at https://svn.apache.org/repos/asf/db/derby/site/trunk/
> Note that we are migrating to svnpubsub independently of the other DB subprojects. They
will migrate soon. Note also that the top level umbrella DB website still needs to migrate
to CMS. We expect that to happen soon too.
> We hope that it is possible for Derby to migrate independently of the other DB subprojects.
If that is not possible, please advise us about how you think that the DB subprojects should
proceed.
> Thanks,
> -Rick

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message