Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 55906 invoked from network); 12 Sep 2006 18:47:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 18:47:28 -0000 Received: (qmail 8493 invoked by uid 500); 12 Sep 2006 18:47:28 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 8449 invoked by uid 500); 12 Sep 2006 18:47:28 -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 8440 invoked by uid 99); 12 Sep 2006 18:47:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 11:47:28 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of francois.orsini@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 11:47:24 -0700 Received: by nf-out-0910.google.com with SMTP id n29so1628488nfc for ; Tue, 12 Sep 2006 11:47:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=I45Hgu6ztl4mosCMq5km4u/25P7uvzapfwhTUIFdYoZjf7nibTQuTeLTqK0TQd8bIP5RjZ9Ho/rstW39RSBqCvXP00qdoYsHIU+UGEigHlY6P5JEEm3sOqFfHEKhGQHHKNtglp8MoCXk3LyLSlXo4m6SoEZbKdqKPZhMFIc0cr8= Received: by 10.49.93.13 with SMTP id v13mr10041569nfl; Tue, 12 Sep 2006 11:47:02 -0700 (PDT) Received: by 10.48.207.14 with HTTP; Tue, 12 Sep 2006 11:47:02 -0700 (PDT) Message-ID: <7921d3e40609121147q1b1c425at9658975161fe9598@mail.gmail.com> Date: Tue, 12 Sep 2006 11:47:02 -0700 From: "Francois Orsini" To: derby-dev@db.apache.org Subject: Re: Compiling 10.2 Release Notes In-Reply-To: <4506F69D.6030700@sun.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_292797_28049568.1158086822819" References: <4506F69D.6030700@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_292797_28049568.1158086822819 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 9/12/06, Rick Hillegas wrote: > > At some point, I will need to bundle Release Notes into the 10.2 > distributions. Here's a proposal for what I need to do: > > 1) Create a new top-level text file next to LICENSE and README. I'd like > to call this file RELEASE-NOTES. Minor nit but it should probably be RELEASE-NOTES.txt (note the added extension) - This is what am seeing from other Apache projects. You may have meant it already & implicitly. 2) Fill up this file with the following three sections: > > a) Features. These would be brief descriptions culled from the summary > table on the snapshot wiki page: > http://wiki.apache.org/db-derby/TenTwoSnapshot Probably something like 'New features' b) Release notes proper. These would be the release notes visible > through the following JIRA filter: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311198 > . > Currently, 22 notes appear in this filter. > > 3) Bug fixes. These would be the one line summaries from issues visible > through the following JIRA filter: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311199 > . > Currently, 373 issues appear in this filter. I think I can discard the > following: > > a) issues which users wouldn't see, such as code cleanup tasks > > b) bug fixes also applied to 10.1.3.1 > > I would like your advice: > > A) Overall, does this sound like a reasonable approach? It does to me. B) Are these filters the right ones or should I edit them? Am assuming that your filter would not pick Documentation JIRA's - I don't think Doc JIRA fixes should be exposed. My 0.02 cents. C) Any tips about how to make this easier? Not sure - Usually release notes always end-up being hand-crafted :) Thanks, > -Rick > ------=_Part_292797_28049568.1158086822819 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 9/12/06, Rick Hillegas <Richard.Hillegas@sun.com> wrote:
At some point, I will need to bundle Release Notes into the 10.2
distributions. Here's a proposal for what I need to do:

1) Create a new top-level text file next to LICENSE and README. I'd like
to call this file RELEASE-NOTES.

Minor nit but it should probably be RELEASE-NOTES.txt (note the added extension) - This is what am seeing from other Apache projects. You may have meant it already & implicitly.

2) Fill up this file with the following three sections:

a) Features. These would be brief descriptions culled from the summary
table on the snapshot wiki page:
http://wiki.apache.org/db-derby/TenTwoSnapshot

Probably something like 'New features'

b) Release notes proper. These would be the release notes visible
through the following JIRA filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311198.
Currently, 22 notes appear in this filter.

3) Bug fixes. These would be the one line summaries from issues visible
through the following JIRA filter:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311199.
Currently, 373 issues appear in this filter. I think I can discard the
following:

a) issues which users wouldn't see, such as code cleanup tasks

b) bug fixes also applied to 10.1.3.1

I would like your advice:

A) Overall, does this sound like a reasonable approach?

It does to me.

B) Are these filters the right ones or should I edit them?

Am assuming that your filter would not pick Documentation JIRA's - I don't think Doc JIRA fixes should be exposed. My 0.02 cents.

C) Any tips about how to make this easier?

Not sure - Usually release notes always end-up being hand-crafted :)

Thanks,
-Rick

------=_Part_292797_28049568.1158086822819--