Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 6 Jan 2014 22:23:51 +0000 (UTC)
From: "Sean Mackrory (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12687516.1389040182690.50193.1389047031927@arcas>
In-Reply-To: <JIRA.12687516.1389040182690@arcas>
References: <JIRA.12687516.1389040182690@arcas>
Subject: [jira] [Commented] (ACCUMULO-2139) Create list of features which
 need manual verification
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863508#comment-13863508 ] 

Sean Mackrory commented on ACCUMULO-2139:
-----------------------------------------

I work primarily on Apache Bigtop, and I've been keeping an eye on Apache Accumulo because I'd quite like to add it to the Bigtop stack at some point in the near future. Hopefully I can be helpful here, and perhaps I'll be more helpful soon :)

Bigtop does do testing on fully-distributed clusters, and that's been valuable to other projects as we provide that kind of testing regularly. We've worked especially closely with Hive, who are actually using some of our projects infrastructure for other automated testing (see http://bigtop01.cloudera.org:8080/view/Hive). I can't speak to which resources remain unspoken for and how those resources have been spoken for in the past, but if you do think there's an opportunity for some beneficial cooperation here, please just make an appearance on the mailing list to discuss it with the community.

Bigtop is currently very much oriented around releases from the "upstream" components - there has been a lot of talk about doing continual testing based on the corresponding "trunk" branches so integration issues and be caught and fixed earlier, but currently Bigtop needs a "release" before it will build everything for you. So it would take a bit of work before Accumulo could easily be built and deployed before a release. Consequently, I think this might not be a perfect fit as Josh Elser is saying. It wouldn't be very feasible I think for Accumulo to wait on some things from Bigtop's side of things before every release.

> Create list of features which need manual verification
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2139
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2139
>             Project: Accumulo
>          Issue Type: Task
>            Reporter: Keith Turner
>             Fix For: 1.6.0
>
>
> If an issue like ACCUMULO-2036 can not be tested automatically, then maybe it should be added to a list of things that must be verified before release.   Where should this list go and what else should be on it?  
> Upgrade seems like another candidate for the list.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)