Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8558B10CCB for ; Tue, 22 Oct 2013 00:10:42 +0000 (UTC) Received: (qmail 45041 invoked by uid 500); 22 Oct 2013 00:10:42 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 45014 invoked by uid 500); 22 Oct 2013 00:10:42 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 44999 invoked by uid 99); 22 Oct 2013 00:10:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 00:10:42 +0000 Date: Tue, 22 Oct 2013 00:10:41 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1797) update release practices to cover multiple Hadoops MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801339#comment-13801339 ] Josh Elser commented on ACCUMULO-1797: -------------------------------------- I'm not sure I agree with what you said [~kturner]. (When I say "we" going forward, I mean the collective Accumulo community, which, when it comes down to it, likely refers to committers.) We haven't really had a good track record for involvement in release testing. Perhaps making a more discrete testing plan for committers to follow on their "flavors of choice" (OS and Java, Hadoop, Zookeeper versions) would get committers more involved? First off, I think that we should be testing Accumulo against each "stable" version of Hadoop at the time of that release -- so, for 1.6.0, this equates to 1.2.1 and 2.2.0. This also defines what I would call "supported". Unless the Hadoop community would do something drastic that would break us (which I would never expect to be the case), I think tracking Apache Hadoop would be the best. I think this also makes management of the hadoop.profile's a bit easier to track/maintain. Zookeeper, I'm less concerned about testing. I'd feel ok testing against the most recent, stable release (3.4.5, presently), but if someone wants to test 3.3.6 too, that'd be good. I just wouldn't want to hold up our releases for not having rigorous testing against 3.3.6. > update release practices to cover multiple Hadoops > -------------------------------------------------- > > Key: ACCUMULO-1797 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1797 > Project: Accumulo > Issue Type: Sub-task > Reporter: Sean Busbey > > if we're going to label Hadoop platforms as supported, we should ensure the release process specifies that tests are run against each of them. -- This message was sent by Atlassian JIRA (v6.1#6144)