db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4855) Automate release publication steps
Date Fri, 12 Nov 2010 17:34:13 GMT

     [ 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-04-aa-copyCgiScript.diff

Attaching derby-4855-04-aa-copyCgiScript.diff. This makes the transformrelnotes target also
create the cgi script for the download page for the new release. Committed at subversion revision

Touches the following file:

M      build.xml

> 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
> 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
> 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.

View raw message