Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 88787 invoked from network); 17 Feb 2010 19:45:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2010 19:45:59 -0000 Received: (qmail 99159 invoked by uid 500); 17 Feb 2010 19:45:58 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 99071 invoked by uid 500); 17 Feb 2010 19:45:57 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 98948 invoked by uid 99); 17 Feb 2010 19:45:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 19:45:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of trawick@gmail.com designates 209.85.210.177 as permitted sender) Received: from [209.85.210.177] (HELO mail-yx0-f177.google.com) (209.85.210.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 19:45:50 +0000 Received: by yxe7 with SMTP id 7so6218861yxe.10 for ; Wed, 17 Feb 2010 11:45:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=4TCc9Th1vzrr91JFjF2lzOHEThaQPbjgxywWxJDlOsw=; b=pXqun3WJ3HHMneVUbLoiHvgNYkiGmk1mZ2gtIgTCD15HywoX/iQotFr1Eg92mI3E8L hQ5+Oay7Hj7fydDBnafeG0B75U/LvjnmxTpVFk8QdUMFMoYkACnb0zSX1fpD4f+sOud9 BfjE+NR6p/lhNLRyBwBCMIOSqpvQfMuN3ZB9M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=nn3Fs8OL02vpOpi3N2b7VYrm9Ru7uEV8ZdRPIBuIj0b47MQuhIcE3GwuOUdC7laF0F rnhRJq+S/hWz6uKw7UD/4qh4WHlQ6JRKusM3wrKQz89kyDmYlH+iF7v43Ii+atFYenQK xTD/Jvm7Cnk+9crckRjvXHZswNXlF5CSACzGY= MIME-Version: 1.0 Received: by 10.101.137.32 with SMTP id p32mr7518231ann.67.1266435929542; Wed, 17 Feb 2010 11:45:29 -0800 (PST) In-Reply-To: References: Date: Wed, 17 Feb 2010 14:45:29 -0500 Message-ID: Subject: Re: What goes in CHANGES and svn log comments? From: Jeff Trawick To: dev@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Feb 17, 2010 at 2:38 PM, Dan Poirier wrote: > On 2010-02-06 at 10:36, Dan Poirier wrote: > >> * In trunk, does CHANGES document the changes from the last stable >> =A0 release, or from the previous alpha release of trunk? =A0That would >> =A0 affect whether backported fixes should be mentioned in trunk CHANGES= . > > Does anyone have comments on this question? An alpha is counted as a release, so upgraders from 2.3.6 alpha to 2.3.7 alpha would expect to see what changed without looking at what was backported to 2.2.x and delivered in both release streams.