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 >> [DISCUSSION] Combine committer lists in Common/HDFS/MapReduce


Copy link to this message
-
Re: [DISCUSSION] Combine committer lists in Common/HDFS/MapReduce
On 08/06/2010 02:02 PM, Chris Douglas wrote:
> Thoughts?

To my thinking, a single set of committers should manage a product.  A
product is something that's released.  Currently, we still branch and
release Common, HDFS and MapReduce together, so I regard them as a
single product and hence believe they should have a single set of
committers.  If/when we start to release them separately then we can
consider splitting committer lists.  Even then, we don't have to split
them, since a single set of committers can manage multiple products.  In
fact, I don't see a strong case for splitting committer lists until
these become separate TLPs.  (The other Hadoop subprojects with separate
committer lists ought to become TLPs, but that's a separate discussion.)

Doug
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