[
https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4855:
---------------------------------
Attachment: derby-4855-03-aa-cgiTemplate.diff
Attaching derby-4855-03-aa-cgiTemplate.diff. This patch introduces a template
cgi script for creating download pages. Committed at
subversion revision 1034474.
Currently, the release instructions say that you should create a cgi script for
the new release by copying the cgi script from an old release. This patch
formalizes the notion of a template script, making it possible to automate the
creation of the new script.
Touches the following files:
----------
A src/documentation/content/xdocs/releases/release-template.cgi
The new template script.
----------
M build/site/releases/release-10.6.2.1.cgi
This is the built version of the 10.6.2.1 cgi script. It turns up checked-out
in my website client. I think this is just a line-ending issue. The original
script was probably produced on a Windows box.
> Automate release publication steps
> ----------------------------------
>
> Key: DERBY-4855
> URL: https://issues.apache.org/jira/browse/DERBY-4855
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Rick Hillegas
> Attachments: derby-4855-01-aa-docszip.diff,
> derby-4855-02-ab-releaseNotesTransformer.diff,
> derby-4855-03-aa-cgiTemplate.diff
>
>
> Right now, producing a Derby release involves 3 major chunks of work:
> 1) Producing the release notes (happens the week before the first release
> candidate is produced)
> 2) Producing release candidates (and submitting them to community vote)
> 3) Publishing the release distributions (after the community approves a
> candidate)
> This JIRA organizes work needed to automate the tasks which are part of step
> (3). Those steps are described here:
> http://wiki.apache.org/db-derby/ReleasePublication
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
