[
https://issues.apache.org/jira/browse/DERBY-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5388:
-----------------------------------
Attachment: archive-release.py
First attempt at automating the required tasks to archive a release. We might
want to testdrive this tool on 10.8.1.2 when 10.8.2 has been deployed. The
approach isn't terribly elegant, but if we keep the HTML/XML as it is today it
should work fine (the tool is dependent on a few special strings).
I'm thinking the tool can live in site-trunk/scripts.
To run the script (after you have copied it into the directory mentioned
above), type:
python scripts/archive-release.py 10.8.1.2
Patch ready for review.
I don't know if this is automation enough, but it will at least take away the
error-prone manual search-and-replace that we currently rely on.
I think it would be best to run this script after the new release has gone live
- not at the time of deployment.
Do people agree with this?
We also have to come up with guidelines for how to deal with maintenance
releases off older branches. For instance, for how long would we want to mirror
a release off the 10.7 branch if we released one in October (after 10.8.2)?
We can also "archive" the release immediately on deployment, but that gives it
less visibility on the web site and requires a slightly modified process.
> 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
> 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
