[
https://issues.apache.org/jira/browse/DERBY-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5388:
-----------------------------------
Issue & fix info: [Patch Available]
Assignee: Kristian Waagan
> Write tool to automate archive process for old release pages
> ------------------------------------------------------------
>
> Key: DERBY-5388
> URL: https://issues.apache.org/jira/browse/DERBY-5388
> Project: Derby
> Issue Type: Improvement
> Components: Web Site
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: archive-release.py
>
>
> Although release files themselves are automatically copied to the ASF
> archive, several further actions most be taken to update the web site when a
> release is archived.
> In short:
> a) update the download page itself
> b) remove cgi script
> c) update links to point to the archive in the HTML file
> d) remove CGI-enabling code in the the HTML file
> I'm hoping steps b - d can be automated. It's not clear to me how/where to
> integrate this yet (i.e. in the ant targets in the code repos, or as a script
> in the web site repos), but I think the process we want to follow may dictate
> that. We probably don't want to remove existing, working pages/links before
> we have verified that the new ones are working. Verification takes a while,
> since we have to wait for the changes to propagate.
> The reason for this suggestion is that several issues have been logged by the
> ASF infra team for problems with the release pages. There has also been
> errors which are most likely caused by "finger trouble" when manually editing
> the web pages.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
