[jira] [Updated] (DERBY-4855) Automate release publication steps

["Rick Hillegas (JIRA)" <ji...@apache.org>]

     [ 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-06-aa-distributionLinks.diff

Attaching derby-4855-06-aa-distributionLinks.diff. This patch fixes a couple targets in the template for the distribution links used by the ReleaseNotesTransformer tool. Committed to these branches at these subversion revisions:

1430291 - trunk
1430294 - 10.9
1430299 - 10.8
1430301 - 10.7

                
> 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, derby-4855-06-aa-distributionLinks.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira