Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EC25E110A8 for ; Fri, 23 May 2014 14:28:49 +0000 (UTC) Received: (qmail 24765 invoked by uid 500); 23 May 2014 14:28:49 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 24720 invoked by uid 500); 23 May 2014 14:28:49 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 24712 invoked by uid 99); 23 May 2014 14:28:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 14:28:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of josh.elser@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-qc0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2014 14:28:42 +0000 Received: by mail-qc0-f180.google.com with SMTP id i17so8004451qcy.25 for ; Fri, 23 May 2014 07:28:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=BVBqYXVws4Jwt74IOs6cNMS+VUm7cXSnO0mo/TNGms0=; b=GW568W0ieL105zX78n5de1MEzFWsLk+SSzb+IOz0RUGCNbV+EmfmRr9p2H6Wxr6w1a kVEU7U0BieToonMvyX9oc6UcCXAuUFcpOTVhWXPi4gMRr+aD+CN1c+ZLYqS/m9opRxJN mqLibeV9GJgLei4aQca/2gAyPW40+4W1OfXBMDx7mEgNyKXXIuZ3MBr0pDF+MgiRvicB eNWPfg5hU5NvWvhJREXszEUdZEIIwDYV3pQDeFqFM6aE/MlJdgoSMcpbFQaKoSHzmlLZ qOJQfTF9FqcG62Kkq7aAx7wsrb1btOSw493DqW0dgS+QofaUBwoldEbpp8hqo0QWsmN2 OSxA== X-Received: by 10.140.43.100 with SMTP id d91mr6802227qga.11.1400855302050; Fri, 23 May 2014 07:28:22 -0700 (PDT) Received: from HW10447.local (pool-71-166-48-47.bltmmd.fios.verizon.net. [71.166.48.47]) by mx.google.com with ESMTPSA id f3sm5106622qag.7.2014.05.23.07.28.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 May 2014 07:28:21 -0700 (PDT) Message-ID: <537F5B04.4020706@gmail.com> Date: Fri, 23 May 2014 10:28:20 -0400 From: Josh Elser User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: dev@accumulo.apache.org Subject: Re: Thinking about 1.5.2 References: <537F5933.40800@gmail.com> <428583291.20780220.1400855016355.JavaMail.root@comcast.net> In-Reply-To: <428583291.20780220.1400855016355.JavaMail.root@comcast.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Dave, can you wrangle these? Add the fixVersion=1.5.2 for still-open tickets, re-open closed tickets and add a fixVersion=1.5.2, or make a new ticket that references the other tickets that you mention. If we have them marked in JIRA, it's more likely that someone will get them fixed up for 1.5. On 5/23/14, 10:23 AM, dlmarion@comcast.net wrote: > There are some fixes that I have been making in 1.6.1 that revolve around the VFS ClassLoader. 1.5 is affected, so these could be backported if someone wants/needs them. > > > ----- Original Message ----- > > From: "Josh Elser" > To: "dev" > Sent: Friday, May 23, 2014 10:20:35 AM > Subject: Thinking about 1.5.2 > > Ladies and gents, > > We're coming up on about 2 months since 1.5.1 was cut. I'd like to start > thinking about 1.5.2. We have 65 issues already resolved which is pretty > good, IMO. Hopefully this will help kick us into a more regular release > cadence. > > It looks like we have one ticket currently marked as in progress (Sean - > ACCUMULO-2806, Keith - ACCUMULO-2766, myself - ACCUMULO-2785, as well as > some patches ACCUMULO-2758 ACCUMULO-2827). What do we think is a > sufficient time length to get these done? 2 weeks? > > How about we try to freeze things on June 9th and get some testing done > for, hopefully a release in a week or two after that. I'm happy to take > the RM position on this one again, but would be happy to help someone > else through it if they're interested as well. Thoughts? > > - Josh > >