Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 52765 invoked from network); 17 Mar 2008 14:08:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Mar 2008 14:08:15 -0000 Received: (qmail 28161 invoked by uid 500); 17 Mar 2008 14:08:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 28126 invoked by uid 500); 17 Mar 2008 14:08:12 -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 28117 invoked by uid 99); 17 Mar 2008 14:08:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2008 07:08:12 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of m.v.lunteren@gmail.com designates 64.233.182.186 as permitted sender) Received: from [64.233.182.186] (HELO nf-out-0910.google.com) (64.233.182.186) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2008 14:07:35 +0000 Received: by nf-out-0910.google.com with SMTP id d3so1983529nfc.15 for ; Mon, 17 Mar 2008 07:07:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=hxgc2bW4X07xycTcww4gRrTyHFjGMGBRAl+rLr65gPY=; b=N4QdG/2m7F/frBhhQwSgNmB1g5bLAWkBvYO8Aatfhz8pv47FzVD0D4zvCrOGUgEpC60bYfp0g1DdlXvD+HY2vjqS4TGswoy8BrpxTtpmrLwk7LRU6z6iz3+b3BMCmwI2r41q2JhPA7jMCQmrae5LPG+oJWb4AvwnefsLbZhapuA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LMhF0btlLCzlmrUIRf4iLvkWuBIRSddKLLncE5sFRVMlAlCIO0NkSnPWJGJDTCpzVjahMpnZm1dB9/zMuFZYQ8ksFvM2mJ+4L79do44oMr2/iZO6pmu8s4DbYNasc1NepyqP9Ai0xvI4BZzhkTy8tRXgrs1h3I5xtPqkoyeUpQg= Received: by 10.78.201.8 with SMTP id y8mr42489743huf.18.1205762863428; Mon, 17 Mar 2008 07:07:43 -0700 (PDT) Received: by 10.78.161.8 with HTTP; Mon, 17 Mar 2008 07:07:43 -0700 (PDT) Message-ID: Date: Mon, 17 Mar 2008 07:07:43 -0700 From: "Myrna van Lunteren" To: derby-dev@db.apache.org Subject: Re: Question about generating release notes In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org On 3/14/08, Dyre.Tjeldvoll@sun.com wrote: > Dyre.Tjeldvoll@Sun.COM writes: > > > I have not yet looked through all 10.4 issues with a release note, but I > > wanted to do a "dry-run" generation just to check that everything works. > > > > I'm looking at > > http://wiki.apache.org/db-derby/ReleaseNoteProcess > > > > where it says: > > > > Report - Generates two xml JIRA reports: > > o > > > > fixedBugsList.xml - This is the list of issues addressed by the release > > o > > > > releaseNotesList.xml - This is the list of issues bearing detailed releaseNotes.html explanations. > > > > > > Just how do I create those two xml files? Do I get them from a Jira > > filter? Or do I need to create them by hand? > > So I figured out that the release notes generator expects the type of > xml file you can get from a Jira filter, so I expect that's what I > should do. > > But are there pre-defined filters which I should use for > fixed bugs and release note issues, respectively? If not; which criteria > should I use? > > And what if an issue is marked with 'Existing Application Impact' ONLY, > and there is no releas note for it? Should it be mentioned somewhere? > > -- > dt > For what it's worth, when I was doing the first trials for 10.3 I ran into major trouble with this - mostly because I was attempting to use MS Explorer as my browser, which didn't allow me to save as xml. To get past this, I had created a xmlfile generator, which would get xml and manipulate the records after. But it wasn't a very robust tool and it got to be very confusing with multiple candidates. Neither Rick (for the final 10.3.1.4) nor Kathey (for 10.3.2.1) tried to do this and the references were removed from the wiki. I think at 10.3 trial versions I reviewed the 'Existing Application Impact' issues, and decided that most merited a release note...I think however, that existing application impact flag may possibly be left in place for savvy JIRA users who could search JIRA for items marked that way. Myrna