Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 87374 invoked from network); 30 Apr 2007 19:09:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Apr 2007 19:09:51 -0000 Received: (qmail 55666 invoked by uid 500); 30 Apr 2007 19:09:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 55639 invoked by uid 500); 30 Apr 2007 19:09:57 -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 55630 invoked by uid 99); 30 Apr 2007 19:09:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 12:09:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.42.249] (HELO nwk-ea-fw-1.sun.com) (192.18.42.249) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 12:09:49 -0700 Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l3UJ9TET005686 for ; Mon, 30 Apr 2007 12:09:29 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JHB00L01RQWDW00@d1-sfbay-09.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Mon, 30 Apr 2007 12:09:29 -0700 (PDT) Received: from [192.9.61.197] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JHB004FPRVSJM54@d1-sfbay-09.sun.com> for derby-dev@db.apache.org; Mon, 30 Apr 2007 12:09:28 -0700 (PDT) Date: Mon, 30 Apr 2007 12:11:26 -0700 From: Rick Hillegas Subject: Re: new format for release notes In-reply-to: <46363CBB.9090506@sun.com> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <46363F5E.6080909@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <46361D9E.1000402@sun.com> <46361ED1.4070801@amberpoint.com> <46363CBB.9090506@sun.com> User-Agent: Thunderbird 1.5.0.5 (X11/20060828) X-Virus-Checked: Checked by ClamAV on apache.org Rick Hillegas wrote: > Knut.Hatlen@Sun.COM wrote: >> Bryan Pendleton writes: >> >> >>>> 2) The format of that html file can be found in the releaseNote.html >>>> attached to DERBY-2570. >>> Is that correct? How will we know that the releaseNote.html that is >>> attached to DERBY-2570 is different from the releaseNote.html that >>> is attached to any other issue? >>> >> >> I think we still mark the issues that need a release note with the >> "Release Note Needed" flag, so it should be clear that the file attached >> to DERBY-2570 is not a release note (but renaming it to template is >> probably a good idea). Or does the proposal mean that we stop using the >> flag? >> >> > Hi Knut Anders, > > Yes, the proposal is that we still need to turn on the "Release Note > Needed" flag. That will be the pamphlet-generator's clue that an issue > ought to have a releaseNote.html attached. So let me take another > crack at stating the proposal: > > 1) For JIRAs which need a release note, you should turn on the > "Release Note Needed" flag and attach a file called "releaseNotes.html". > > 2) The template for releaseNotes.html lives in > tools/release/templates/releaseNote.html. > > 3) As you improve the wording of your release note, you simply attach > a new version of releaseNotes.html. The release documentation will > include the last version of the release note. > > Regards, > -Rick > Sigh. Let me restate that and call the attached file "releaseNote.html" rather than "releaseNotes.html". 1) For JIRAs which need a release note, you should turn on the "Release Note Needed" flag and attach a file called "releaseNote.html". 2) The template for releaseNote.html lives in tools/release/templates/releaseNote.html. 3) As you improve the wording of your release note, you simply attach a new version of releaseNote.html. The release documentation will include the last version of the release note.