Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F4CF7D60 for ; Mon, 12 Sep 2011 16:25:59 +0000 (UTC) Received: (qmail 6135 invoked by uid 500); 12 Sep 2011 16:25:59 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 5937 invoked by uid 500); 12 Sep 2011 16:25:58 -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 5930 invoked by uid 99); 12 Sep 2011 16:25:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2011 16:25:58 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of m.v.lunteren@gmail.com designates 209.85.216.46 as permitted sender) Received: from [209.85.216.46] (HELO mail-qw0-f46.google.com) (209.85.216.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2011 16:25:52 +0000 Received: by qwb7 with SMTP id 7so3503347qwb.33 for ; Mon, 12 Sep 2011 09:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=sXE5QJp93f5mU8i6lBkZjqYWkKbC92vbiHf0W7DwIdw=; b=beF60goFWH30QRk9efRL2i+jX4exw8ACCrOPXGDZ/5Z8o9/5hvsymptRNIHR/ZMxz7 8OAyPhV4FT9K0loNzZjtu8iq667Ljpy9USEepaTxIwS1qPWIDLn59YpPVB2SC27h4iTY YGVns7e5PXFuW4wbKSwsmPDKudIViWvVBF6uQ= MIME-Version: 1.0 Received: by 10.68.8.66 with SMTP id p2mr2644556pba.442.1315844731011; Mon, 12 Sep 2011 09:25:31 -0700 (PDT) Received: by 10.68.62.10 with HTTP; Mon, 12 Sep 2011 09:25:30 -0700 (PDT) In-Reply-To: <4E6E0279.4000702@oracle.com> References: <4E6E0279.4000702@oracle.com> Date: Mon, 12 Sep 2011 09:25:30 -0700 Message-ID: Subject: Re: First Draft 10.8.2 release notes From: Myrna van Lunteren To: derby-dev@db.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Sep 12, 2011 at 6:00 AM, Rick Hillegas w= rote: >>> On Fri, Sep 9, 2011 at 8:53 AM, Dag H. Wanvik=A0= wrote: >>> [...There] are not user visible changes and could be left out, I think. >>> >>On 9/9/11 2:40 PM, Myrna van Lunteren wrote: >>[...]I didn't think I should manually adjust the release notes. >> [...] > If people feel strongly that the release notes are too verbose, then we > should discuss how to flag noise issues in JIRA. That way we can > programmatically exclude them from the filters. It's late in the day to d= o > this for 10.8.2 but we could consider this change for 10.9. > > Thanks, > -Rick > I don't want to do this for 10.8.2. I think perhaps a 'development only' or 'internal' flag could be used to mark issues that would not be useful to end-users. I was wondering whether we want to go back to having 2 files or have 1 Release Notes file with 2 sections. (We had at one point the "changes" file in addition to the release notes, but if I remember correctly, the difference between the two wasn't clear). I lean slightly in favor of 2 different files - so that someone can pass on only the end-user relevant file. Perhaps the other file could be called e.g. Derby_Project_Notes...(I find it difficult to come up with a name that clearly separates developers using derby from developers of derby). But now first I need to make a release. Myrna