Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 71372 invoked from network); 19 Oct 2010 14:38:15 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 19 Oct 2010 14:38:15 -0000 Received: (qmail 79247 invoked by uid 500); 19 Oct 2010 14:38:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 79193 invoked by uid 500); 19 Oct 2010 14:38:14 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 79185 invoked by uid 99); 19 Oct 2010 14:38:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 14:38:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Oct 2010 14:38:11 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9JEbn4f001525 for ; Tue, 19 Oct 2010 14:37:49 GMT Message-ID: <23658044.47491287499069696.JavaMail.jira@thor> Date: Tue, 19 Oct 2010 10:37:49 -0400 (EDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-4855) Automate release publication steps MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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 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.