Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 75387 invoked from network); 22 Mar 2007 09:43:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Mar 2007 09:43:35 -0000 Received: (qmail 55974 invoked by uid 500); 22 Mar 2007 09:43:42 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 55948 invoked by uid 500); 22 Mar 2007 09:43:42 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 55939 invoked by uid 99); 22 Mar 2007 09:43:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 02:43:42 -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 tom.e.white@gmail.com designates 64.233.184.227 as permitted sender) Received: from [64.233.184.227] (HELO wr-out-0506.google.com) (64.233.184.227) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 02:43:33 -0700 Received: by wr-out-0506.google.com with SMTP id i28so584350wra for ; Thu, 22 Mar 2007 02:43:12 -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=DBNs1Gp6JgbulLbaaFbtwSoYC0SQ2G0x4gucPEUESU5TIdpeWuw0zZ0MUZo4hDiYe8dPO/OzMRvDFkRxIxFeMXHlpbzfeMQoShqRgCM4qHS9N7joEoRS1sfbXnNwZbnuWJbG/MIqUa4ilUTDJbL95VPiPrIE5fkYrOUld3i9W9w= 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=FTy0MyFl7U6EilaokvnblUqsd+/4bh5NsGkUH7FdEo1/SU13mQa2BR6gvadN0Sf3bLhW1vXMCztNShFESoMI27nC/o9xxWlbMg51tqfIY00LJzlDj/rtu3RbQ+6TX+leLUoIfH/8Q8Hvdbkr3namBw/LX1lE/RCwTOFOL/kVVig= Received: by 10.114.155.1 with SMTP id c1mr527379wae.1174556591835; Thu, 22 Mar 2007 02:43:11 -0700 (PDT) Received: by 10.114.13.13 with HTTP; Thu, 22 Mar 2007 02:43:11 -0700 (PDT) Message-ID: Date: Thu, 22 Mar 2007 09:43:11 +0000 From: "Tom White" To: hadoop-dev@lucene.apache.org Subject: Re: committing to 0.13.0 (trunk) In-Reply-To: <94080AC3-0F40-4F44-B411-65D3C5EB13E5@yahoo-inc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <94080AC3-0F40-4F44-B411-65D3C5EB13E5@yahoo-inc.com> X-Virus-Checked: Checked by ClamAV on apache.org I was holding off committing while waiting to see if we need a 0.12.2 release. It looks like we do for https://issues.apache.org/jira/browse/HADOOP-1135 (which I've now committed). So, I would propose we release 0.12.2 tomorrow (Friday) or the weekend, then catch up on the 0.13.0 backlog next week. Thoughts? Tom On 22/03/07, Nigel Daley wrote: > Clearly we have a long backlog of patches for 0.13.0. At last count > it was 18. > > I run a large suite of benchmarks every night on trunk and I'm > concerned that if we apply them all at once, we won't be able to > identify individual patches if/when problems arise. > > Are committers willing to spread out commits of these patches over 2 > days? > > If so, here's a proposed schedule: > > Thursday 22 (these all apply given this order): > 702 > 1135 > 1101 > 1071 > 1116 > 1120 > 1064 > 1063 > 1137 > > Friday 23 > the rest that will apply > > Thoughts? > > Cheers, > Nige >