[
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-05-aa-cliXconf.diff
Attaching derby-4855-05-aa-cliXconf.diff. This patch makes the
transformrelnotes target wire the new download page into the website-building
instructions so that it will be picked up when you build the Derby website.
Committed at subversion
Touches the following files:
----------
M java/build/org/apache/derbyBuild/ReleaseNotesTransformer.java
Logic to update src/documentation/conf/cli.xconf.
----------
M build.xml
Added an extra argument to the transformation ant task.
> 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, derby-4855-04-aa-copyCgiScript.diff,
> derby-4855-05-aa-cliXconf.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.
