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
HBase >> mail # dev >> DISCUSSION: Move to GIT?


Copy link to this message
-
Re: DISCUSSION: Move to GIT?
On Fri, Oct 25, 2013 at 11:42 AM, Enis Söztutar <[EMAIL PROTECTED]> wrote:

> > I'd suggest we maintain the same commit style (straight line rebased
> commits per release branch, branches off trunk for major features) after
> the move to git as opposed to the github style (lots of branch/merges).
>
> +1 to that as well. Having multiple commits and merge commits per jira will
> complicate commit log digging a lot. And we do not care about a patch's
> individual history.
>
> Will FB guys ok with this? How does this affect 0.89-fb branch.
>

We could leave old branches on svn.
St.Ack
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