You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2010/11/16 18:29:15 UTC

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

    [ https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932546#action_12932546 ] 

Rick Hillegas commented on DERBY-4855:
--------------------------------------

Ported 1035700 from trunk to 10.7 branch at subversion revision 1035702.

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