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

Keith Turner commented on ACCUMULO-1797:
----------------------------------------

bq. 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?

Are you looking for something more than the testion section on the [relase 
page|http://accumulo.apache.org/governance/releasing.html]?  If so I would be 
happy to provide more detail.   

bq. 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.

I would love for release testing against 1.2.1 and 2.2.0 to be done, I am not 
against testing on multiple versions.  Below are my thoughts : 

 * Doing release testing takes a lot of time, If only one person decides to do 
this I don't its fair for the community to require anything of them.  The 
community should be thankful for their contribution.  I hope more people do 
release testing and I will be happy to help anyone who wants to tackle it.  I 
suppose another way of looking at it, is that if we do require it then it may 
force someone to take it on inorder to get a release out?  In the case that no 
one does this, then what do we do?
 * Whatever release testing we do should be documented.  We have not really 
done this in the past.  I think this information would be very useful.

There was earlier discussion we were having where we trying to decide if it was 
ok to support one commercial flavor of Hadoop and not another.   In this thread 
[~benson_basis] advised that we have the option to take whatever is 
contributed.   If code, documentation, etc are contributed to support X and Y, 
but not Z then thats what we have.  There is no need to wait for someone to 
contribute code and documentation for Z.  Also we do not need to drop support 
for X and Y because no one contributed anything for Z.  





> 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)

Reply via email to