Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 19610 invoked from network); 20 Jun 2007 02:28:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jun 2007 02:28:21 -0000 Received: (qmail 16608 invoked by uid 500); 20 Jun 2007 02:28:25 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16391 invoked by uid 500); 20 Jun 2007 02:28:24 -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 16382 invoked by uid 99); 20 Jun 2007 02:28:24 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 19:28:24 -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.247 as permitted sender) Received: from [209.85.132.247] (HELO an-out-0708.google.com) (209.85.132.247) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 19:28:20 -0700 Received: by an-out-0708.google.com with SMTP id c8so3961ana for ; Tue, 19 Jun 2007 19:27:59 -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:mime-version:content-type:content-transfer-encoding:content-disposition; b=n6TuLHQLRORMpGYPvNl7D4IPk8ypC30IyaQzsNT/iA00DUy+xTgxEw7N/S0XhdagVgYuVuZBdnm2iqiJSiOymG4q/czpWG68vOmMYdbh0E3M1lLhxu4nLmG3LTqXGVuAo9cdKCitnA6jDHHMBjbmMhffdUNfwW2qbQV2j3tF/p8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=kNiwZYtFbiVFiLa71IdU4TDlFREiW0CS+/0WzBc40CNA+EtaXCu80Rgs8w/XiTYnmYV8v0mt/hJtPM3rVClMlpH6sSw6RumBD2L0MFjOSp2enhfPMxF1h+Rtc66+zw9BrucT2F/dhjVj9E5rF1WlOYKsx3qp5ZBOioreoTJD2I4= Received: by 10.100.107.2 with SMTP id f2mr75785anc.1182306479527; Tue, 19 Jun 2007 19:27:59 -0700 (PDT) Received: by 10.100.91.9 with HTTP; Tue, 19 Jun 2007 19:27:59 -0700 (PDT) Message-ID: Date: Tue, 19 Jun 2007 19:27:59 -0700 From: "Myrna van Lunteren" To: derbydev Subject: Jira...Release Note Needed & Existing Application Impact MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi, I've been struggling with the semantics/use/purpose of the flags, in particular 'Existing Application Impact' and 'Release Note Needed'... I am wondering if we should have a short hint behind the flags. Something like: Patch Available: indicates that a patch is available for review and/or commit. Gets picked up by daily automated mail. Existing Application impact.An existing application can be impacted by the solution to this issue. Regression; the behavior described is worse than in previous versions/builds. Release Note Needed: indicates a releaseNote.html is/should be attached. The releaseNote.html will be automatically included in the RELEASE-NOTES.html at release time when this flag is on. Myrna