Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # general >> Defining Hadoop Compatibility -revisiting-


Copy link to this message
-
Re: Defining Hadoop Compatibility -revisiting-

On May 13, 2011, at 2:55 PM, Doug Cutting wrote:

> On 05/13/2011 07:28 PM, Allen Wittenauer wrote:
>> If it has a modified version of Hadoop (i.e., not an actual Apache
>> release or patches which have never been committed to trunk), are
>> they allowed to say "includes Apache Hadoop"?
>
> No.  Those are the two cases we permit.  We used to say that it was
> enough for a patch to be in Jira, but Roy clarified last year that
> committed to trunk is a better line, since that means the code has been
> reviewed and accepted by the community.
So what do we do about companies that release a product that says "includes Apache Hadoop" but includes patches that aren't committed to trunk?
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB