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 02F8810AB2 for ; Fri, 6 Mar 2015 21:55:37 +0000 (UTC) Received: (qmail 14723 invoked by uid 500); 6 Mar 2015 21:55:31 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 14677 invoked by uid 500); 6 Mar 2015 21:55:31 -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 14663 invoked by uid 99); 6 Mar 2015 21:55:31 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2015 21:55:31 +0000 Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id A0B581A026E for ; Fri, 6 Mar 2015 21:55:31 +0000 (UTC) Received: by iebtr6 with SMTP id tr6so15986258ieb.4 for ; Fri, 06 Mar 2015 13:55:30 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.42.120.2 with SMTP id d2mr12751414icr.5.1425678930939; Fri, 06 Mar 2015 13:55:30 -0800 (PST) Received: by 10.107.173.167 with HTTP; Fri, 6 Mar 2015 13:55:30 -0800 (PST) In-Reply-To: References: Date: Fri, 6 Mar 2015 16:55:30 -0500 Message-ID: Subject: Re: [DISCUSS] Establishing a contrib repo for upgrade testing From: Adam Fuchs To: dev@accumulo.apache.org Content-Type: multipart/alternative; boundary=90e6ba614f423e99310510a5be71 --90e6ba614f423e99310510a5be71 Content-Type: text/plain; charset=UTF-8 I've seen some of the problems this has found, and I'm all for it! Are there opportunities to share this project with other projects? Would this be something that starts out as a contrib and then graduates to top level project over time? Adam On Fri, Mar 6, 2015 at 10:15 AM, Sean Busbey wrote: > Hi Accumulo! > > Cloudera has recently made public some code used for doing correctness > testing for Accumulo installations across upgrades[1]. The project contains > simple data load and verification tools as well as a rudimentary upgrade > test automation script. > > We would like to donate this code to the ASF and use it as a starting place > for a contrib repository focused on testing Accumulo across versions > generally. If the PMC is interested, I'd be happy to take point on the > necessary paperwork for IP clearance[2] following an appropriate vote. > > Though simple, this upgrade testing has already found issues around 1.4 -> > 1.5 -> 1.6 and 1.4 ->1.6 upgrades in the past. There are some obvious > points of clean up that need to happen (vendor specific references in docs, > artifacts, and packages), and I'd be happy to take point on that work as > well. I think it would make a good foundational layer for our future needs > and would give us a place where we could revitalize the work from > ACCUMULO-2145. > > Thoughts? > > [1]: https://github.com/cloudera/accumulo-upgrade-test/ > [2]: http://incubator.apache.org/ip-clearance/ > > -- > Sean > --90e6ba614f423e99310510a5be71--