hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enis Söztutar <e...@apache.org>
Subject Re: Public GitHub tree for HBASE-10191 work
Date Thu, 20 Feb 2014 02:26:22 GMT
Sounds good.

We had a working branch for HBASE-10070 in github (that is also publicized
this way), and now we moved to an svn branch so that commits are going to
that branch after reviews in jira. We also have hbase-10070 release tag in
jira for assigning fix versions to issues while resolving them. This has
worked so far.

The most painful thing is to rebase the patches, because the base patches
change because of review comments, but it is not unmanageable.


On Wed, Feb 19, 2014 at 6:17 PM, Andrew Purtell <apurtell@apache.org> wrote:

> On Wed, Feb 19, 2014 at 5:35 PM, Nick Dimiduk <ndimiduk@gmail.com> wrote:
> > I would also recommend you take an aggressive stance on rebasing this
> > branch onto trunk to keep things fresh. You'll need to work out the
> details
> > with your collaborators though.
> >
> Agreed. I'd like to ultimately keep the work apart as a stack of patches
> floating atop HBase trunk, rather than have a bunch of small commits with
> poorly descriptive commit messages threaded throughout branch history.
> Maybe a weekly Sunday rebase (perhaps with squashing) and force push would
> not be too onerous.
> --
> Best regards,
>    - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message