db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-6007) Migrate Derby website to new Apache website publication machinery
Date Tue, 14 May 2013 17:31:17 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas closed DERBY-6007.

> Migrate Derby website to new Apache website publication machinery
> -----------------------------------------------------------------
>                 Key: DERBY-6007
>                 URL: https://issues.apache.org/jira/browse/DERBY-6007
>             Project: Derby
>          Issue Type: Improvement
>          Components: Web Site
>            Reporter: Rick Hillegas
>         Attachments: derby-6007-01-aa-prepForDocsCheckin.diff
> As of January 2013, the Apache website will no longer be refreshed from the /www/db.apache.org/derby
directory tree on minotaur. Instead, projects will need to put their website content under
subversion control and tell the Infrastructure team where that subversion repository is. Most
of Derby's website is subversion controlled. However, the docs and alpha javadoc directories
are not. We will need to put docs and alpha javadoc under subversion control along with the
rest of the Derby website. Then we will need to file an issue, telling the Infrastructure
team where our content lives. For an example of such an issue, see https://issues.apache.org/jira/browse/INFRA-5215

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

View raw message