Re: Proposal to create a branch for the standalone-metastore work

[Alan Gates <al...@gmail.com>]

Since no one seems opposed to this I’ll make the branch today.  I’ll track
it on HIVE-17159, the umbrella JIRA for the standalone metastore.

On Mon, Oct 30, 2017 at 4:17 PM, Owen O'Malley <ow...@gmail.com>
wrote:

> Alan,
>    That sounds reasonable. Having development branches rebase relatively
> often leads to a much cleaner final git history that using multiple merges.
> For the first couple rebases of your development branch, you might want to
> tell people just before you do it by sending email out to dev@hive.
>
> Thanks,
>    Owen
>
> On Mon, Oct 30, 2017 at 3:44 PM, Alan Gates <al...@gmail.com> wrote:
>
> > ​I propose that we create a branch to continue the standalone metastore
> > work in.  So far we’ve been doing it in master one patch at a time.
> > However, the speed that we can produce patches outstrips the speed at
> which
> > we can get them reviewed, fully tested, and into master.  I would like to
> > put those patches in a branch so that others can review and contribute,
> > while not inflicting the not yet reviewed patches on master.​
> >
> > I am not proposing to do all the development in the branch with a
> big-bang
> > commit/merge at the end.  That will painful for everyone.  We will
> continue
> > to move patches into master one at a time.  This means we’ll be rebasing
> > the branch from time to time.
> >
> > Thoughts?  If there aren’t any objections I’ll do this in a few days.
> >
> > Alan.
> >
>