hive-dev mailing list archives

Hi Ashutosh,
My +1 for the proposal for creating a separate branch for feature
development.
I do have one question in this regard: how do you plan on keeping this
branch in sync with the trunk? If the branch is allowed to diverge
indefinitely, it is likely that the build from it will lag in features and
fixes that are otherwise available on the trunk. It will be great if you
could get the branch to first synchronize with the trunk and then follow a
policy where there are periodic merges from the trunk into the development
branch.
Regards,
Arvind Prabhakar
On Fri, Feb 1, 2013 at 10:11 AM, Ashutosh Chauhan <hashutosh@apache.org>wrote:
> Hi all,
>
> Harish and Prajkta are doing some cool work over at
> https://issues.apache.org/jira/browse/HIVE-896 IMO its a very useful
> feature for the community and our user base. Harish and Prajkta are making
> steady progress on this for much last year in their github repo
> https://github.com/hbutani/hive and much of the feature is now functional.
> However, its quite a bit of work and new code which will take some time
> before being ready for trunk. I propose that we create a new branch so that
> further development of this happens in apache repo instead of github repo.
> This gets us few benefits:
> a) It will avoid the situation we ended up with HiveServer2 where a useful
> new functionality came but in one big patch which made its review and thus
> inclusion in mainline harder than it should have been.
> b) Obvious advantages of development getting done in apache as oppose to
> github which are:
> i) It will make it easier for apache hive community members interested
> in this work (like me) to follow progress.
> ii) It will make it easier for apache hive community members interested
> in this work to contribute.
> iii) It will make it easier for apache community members to review the
> work and provide feedback.
>
> I further propose that we follow Commit-than-review policy for this feature
> branch which will enable contributors to make rapid progress without
> waiting for lengthy review cycles. Hive committers interested in work can
> either review branch any time they want to provide feedback or can wait
> till contributors declare work is complete and make a proposal to merge in
> trunk and than review it than. This anyway is a throwaway branch not
> intended to make releases out of it.
>
> Unless I hear any objections, I will create a branch over the weekend.
>
> Thanks,
> Ashutosh
>