Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 19766 invoked from network); 12 Aug 2009 11:26:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Aug 2009 11:26:30 -0000 Received: (qmail 52349 invoked by uid 500); 12 Aug 2009 11:26:37 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 52321 invoked by uid 500); 12 Aug 2009 11:26:37 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 52296 invoked by uid 99); 12 Aug 2009 11:26:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 11:26:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 12 Aug 2009 11:26:34 +0000 Received: (qmail 19714 invoked by uid 99); 12 Aug 2009 11:26:05 -0000 Received: from localhost.apache.org (HELO fg-out-1718.google.com) (127.0.0.1) (smtp-auth username bdelacretaz, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Aug 2009 11:26:05 +0000 Received: by fg-out-1718.google.com with SMTP id d23so1163290fga.3 for ; Wed, 12 Aug 2009 04:26:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.86.220.9 with SMTP id s9mr8881fgg.40.1250076370240; Wed, 12 Aug 2009 04:26:10 -0700 (PDT) In-Reply-To: References: Date: Wed, 12 Aug 2009 13:26:10 +0200 Message-ID: Subject: Re: How to process patches From: Bertrand Delacretaz To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Aug 12, 2009 at 12:55 PM, J Aaron Farr wrote: > ...It's also a good idea to keep track of which patches go into your > releases by including it in the CHANGELOG. =C2=A0Just referencing the JIR= A > item and the person who suppled the patch is enough.... Note that JIRA can manage that automatically, using the "fix versions" field of issues. See for example https://issues.apache.org/jira/secure/BrowseProject.jspa?id=3D12310710&subs= et=3D-1 -Bertrand