Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 87011 invoked from network); 19 Jul 2008 20:00:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jul 2008 20:00:14 -0000 Received: (qmail 75957 invoked by uid 500); 19 Jul 2008 20:00:13 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 75898 invoked by uid 500); 19 Jul 2008 20:00:13 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 75887 invoked by uid 99); 19 Jul 2008 20:00:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jul 2008 13:00:13 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.202.165.37] (HELO smtpauth13.prod.mesa1.secureserver.net) (64.202.165.37) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 19 Jul 2008 19:59:19 +0000 Received: (qmail 4870 invoked from network); 19 Jul 2008 19:59:37 -0000 Received: from unknown (71.239.140.137) by smtpauth13.prod.mesa1.secureserver.net (64.202.165.37) with ESMTP; 19 Jul 2008 19:59:36 -0000 Message-ID: <488247A6.9060207@rowe-clan.net> Date: Sat, 19 Jul 2008 14:59:34 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Mladen Turk CC: Sander Striker , dev@apr.apache.org Subject: Re: Backport policy, WAS: Re: svn commit: r678140 - /apr/apr/branches/1.3.x/memory/unix/apr_pools.c References: <4881DB83.8080909@apache.org> In-Reply-To: <4881DB83.8080909@apache.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mladen Turk wrote: > Sander Striker wrote: >>> >>> Modified: >>> apr/apr/branches/1.3.x/memory/unix/apr_pools.c >> >> This is just an example, I'm seeing a change land on trunk and a >> minute later on 1.3.x. What's our backport policy? Do we just commit >> to trunk and 1.3.x, or are we going to go a route where we get review >> prior to backporting? Think httpd STATUS... >> > > I usually wait for a day or two before committing to 1.3.x or 1.2.x > from trunk. This particular one is copy/paste typo and was not observed > until Bojan and myself did some actual hard core testing. > > Think the backporting policy is "act responsible" right now, > or am I wrong here? APR entirely operates under CtR. Fortunately, the pace of development has ensured that these can be reviewed, and our versioning policy avoids debates as in httpd about what "features" can be backported. Since all new features are to trunk only, it's a fairly clean policy. I don't see any reason to move to RtC, but discussion is always welcome.