Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 92767 invoked from network); 23 Apr 2007 02:40:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2007 02:40:12 -0000 Received: (qmail 1267 invoked by uid 500); 23 Apr 2007 02:40:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 1056 invoked by uid 500); 23 Apr 2007 02:40:18 -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 1047 invoked by uid 99); 23 Apr 2007 02:40:18 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2007 19:40:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of m.v.lunteren@gmail.com designates 209.85.132.241 as permitted sender) Received: from [209.85.132.241] (HELO an-out-0708.google.com) (209.85.132.241) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Apr 2007 19:40:11 -0700 Received: by an-out-0708.google.com with SMTP id c25so1551183ana for ; Sun, 22 Apr 2007 19:39:50 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H2ybuO9mCaEa+//NWU6+QxLuamwi5+jBNq+VnJ2TOvAr4e214UNb8PhQnxJbFf5FvyuP+aWcqRos5eUzHXolrMsrP98oTk2PG4zXACvUNeBWJWGrk4KpBFig2Ef7f6VtFs9Kr1YrbvXcEs9K/OE8f8ZQFjP8FRlW3mQ6cLbNHwg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AB/slKKEjPmPWW5JourjsHhJ62xnXvvmZNRmtZLFm2MOKs9GMMJf7VyRGwKePKdL8RXTPNot9BepgwNsEq4OMWjOfKQ/Ijm/nlVFXvht7v4S1tAIb8Liw77cVqbTyx37AtCVJitP6A5xIFkH4tgFGVtoadd0xrIhNR+mzavpLFY= Received: by 10.100.125.5 with SMTP id x5mr3304264anc.1177295990005; Sun, 22 Apr 2007 19:39:50 -0700 (PDT) Received: by 10.100.57.10 with HTTP; Sun, 22 Apr 2007 19:39:49 -0700 (PDT) Message-ID: Date: Sun, 22 Apr 2007 19:39:49 -0700 From: "Myrna van Lunteren" To: derby-dev@db.apache.org Subject: Re: [jira] Commented: (DERBY-2570) Create a utility which generates Release Notes In-Reply-To: <6343804.1177083015297.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3469036.1177082715283.JavaMail.jira@brutus> <6343804.1177083015297.JavaMail.jira@brutus> X-Virus-Checked: Checked by ClamAV on apache.org On 4/20/07, Bryan Pendleton (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/DERBY-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490384 ] > > Bryan Pendleton commented on DERBY-2570: > ---------------------------------------- > > If the release notes are stored in Jira (a sensible, place, I think), then why do they > also need to be stored in the code tree? Seems to violate the Don't Repeat Yourself principle... > Good question. The only thing I can think of is that things in JIRA could still be changed - even when a case is closed - and we can have a saved 'snapshot' sort of file that goes with the release... Myrna