What are folks thoughts about development branches with the branch being
the ticket number?  I think it should continue to follow the bylaws but how
do we vote in the initial commit?

Can a committer just +1 whether the JIRA ticket gets a branch or can we
have it so committer (even if committer is working on the code) can branch
for a ticket so the work can get collaborated on?

I want to create a branch for
https://issues.apache.org/jira/browse/KAFKA-1207 which will likely have 3-4
sub tickets it looks like now (which would be nice to include KAFKA-1206
too if folks have a chance to look at the change so if there are issue they
can get in).

Would it make sense to just create a 0.9 branch and do it under that?

I was thinking of doing a few security ones also.

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/

 
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