Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 72107 invoked from network); 20 Oct 2010 13:45:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Oct 2010 13:45:50 -0000 Received: (qmail 88800 invoked by uid 500); 20 Oct 2010 13:45:49 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 88178 invoked by uid 500); 20 Oct 2010 13:45:47 -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 87572 invoked by uid 99); 20 Oct 2010 13:45:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Oct 2010 13:45:47 +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; Wed, 20 Oct 2010 13:45:46 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9KDjQH7024957 for ; Wed, 20 Oct 2010 13:45:26 GMT Message-ID: <2044107.8841287582326586.JavaMail.jira@thor> Date: Wed, 20 Oct 2010 09:45:26 -0400 (EDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-4857) Utilize the SOAP API to fetch JIRA issue list for release notes generation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Utilize the SOAP API to fetch JIRA issue list for release notes generation -------------------------------------------------------------------------- Key: DERBY-4857 URL: https://issues.apache.org/jira/browse/DERBY-4857 Project: Derby Issue Type: Improvement Components: Build tools Reporter: Kristian Waagan Assignee: Kristian Waagan Somewhat simplified, the release manager (RM) must currently perform the following manual steps to feed the release note generate the data it needs: a) Create manual JIRA filter to select issues addressed by the release. b) Save the filter result to disk as XML. c) Write/modify the XML parser to be able to parse the report. d) Determine and record all JIRA release note attachment ids for the issues requiring a release note. By using the current version of the SOAP API (3.13.5), steps (b) to (d) can be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.