[
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-02-ab-releaseNotesTransformer.diff
Attaching derby-4855-02-ab-releaseNotesTransformer.diff. This adds a new ant
task and target for turning the release notes into a download page after the
vote passes. Committed at subversion revision 1033940.
Currently, the release manager constructs the download page by hand. This
involves merging material from two source html documents and removing material
which the Forrest tool can't handle. The new ant task and target simplify this
process and make it less brittle. To use this new target, do the following. You
will be prompted to supply a little information:
o cd to the root of your code client
o then type "ant transformreleasenotes"
Touches the following files:
--------------
A java/build/org/apache/derbyBuild/ReleaseNotesTransformer.java
New ant task.
--------------
M build.xml
New ant target.
> 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
>
>
> 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.
