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
Drill >> mail # dev >> Proposal: consolidate execwork and master


Copy link to this message
-
Re: Proposal: consolidate execwork and master
+1

With git, working on a private copy of trunk is equivalent of the old style
working on a branch.

On Mon, Jul 15, 2013 at 1:28 PM, Jacques Nadeau <[EMAIL PROTECTED]> wrote:

> The vision of the execwork branch was to maintain a development branch
> and then merge to master once we were happy with the quality and unit
> test completeness of the execwork stuff.  However, it now appears that
> everyone is working in the execwork branch.  Additionally, I've also
> had a number of offhand comments from those less familiar with the
> project who assume that a lack of commits on master means the project
> is less active than it is.  As such, I propose that we merge the
> execwork branch back into master and continue to do our work there.
> With the lastest push of Ben's patches for ValueVectors and the merge
> of DRILL-140 into execwork, execwork includes all the changes in
> master and all tests pass.
>
> Jacques
>
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