You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Sergey Shelukhin <se...@apache.org> on 2015/04/15 23:46:26 UTC
VOTE: move to git
Hi.
We’ve been discussing this some time ago; this time I¹d like to start an
official vote about moving Hive project to git from svn.
I volunteer to facilitate the move; that seems to be just filing INFRA
jira, and following instructions such as verifying that the new repo is
sane.
Please vote:
+1 move to git
0 don’t care
-1 stay on svn
+1.
Re: VOTE: move to git
Posted by pandeeswaran bhoopathy <pa...@me.com>.
+1
-Pandeesh
Sent from my iPhone
> On Apr 15, 2015, at 3:51 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> +1
>
>> On Wed, Apr 15, 2015 at 3:18 PM, Jimmy Xiang <jx...@cloudera.com> wrote:
>>
>> +1
>>
>> On Wed, Apr 15, 2015 at 3:09 PM, Vivek Shrivastava <
>> vivshrivastava@gmail.com
>>> wrote:
>>
>>> +1
>>> On Apr 15, 2015 6:06 PM, "Vaibhav Gumashta" <vg...@hortonworks.com>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> On 4/15/15, 2:55 PM, "Prasanth Jayachandran"
>>>> <pj...@hortonworks.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>>> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <
>> gopalv@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> End the merge madness.
>>>>>>
>>>>>>> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
>>>>>>>
>>>>>>> Hi.
>>>>>>> We’ve been discussing this some time ago; this time I¹d like to
>> start
>>>>>>> an
>>>>>>> official vote about moving Hive project to git from svn.
>>>>>>>
>>>>>>> I volunteer to facilitate the move; that seems to be just filing
>>> INFRA
>>>>>>> jira, and following instructions such as verifying that the new
>> repo
>>> is
>>>>>>> sane.
>>>>>>>
>>>>>>> Please vote:
>>>>>>> +1 move to git
>>>>>>> 0 don’t care
>>>>>>> -1 stay on svn
>>>>>>>
>>>>>>> +1.
>>
Re: VOTE: move to git
Posted by Nick Dimiduk <nd...@gmail.com>.
+1
On Wed, Apr 15, 2015 at 3:18 PM, Jimmy Xiang <jx...@cloudera.com> wrote:
> +1
>
> On Wed, Apr 15, 2015 at 3:09 PM, Vivek Shrivastava <
> vivshrivastava@gmail.com
> > wrote:
>
> > +1
> > On Apr 15, 2015 6:06 PM, "Vaibhav Gumashta" <vg...@hortonworks.com>
> > wrote:
> >
> > > +1
> > >
> > > On 4/15/15, 2:55 PM, "Prasanth Jayachandran"
> > > <pj...@hortonworks.com> wrote:
> > >
> > > >+1
> > > >
> > > >> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <
> gopalv@apache.org>
> > > >>wrote:
> > > >>
> > > >> +1
> > > >>
> > > >> End the merge madness.
> > > >>
> > > >> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
> > > >>
> > > >>> Hi.
> > > >>> We’ve been discussing this some time ago; this time I¹d like to
> start
> > > >>>an
> > > >>> official vote about moving Hive project to git from svn.
> > > >>>
> > > >>> I volunteer to facilitate the move; that seems to be just filing
> > INFRA
> > > >>> jira, and following instructions such as verifying that the new
> repo
> > is
> > > >>> sane.
> > > >>>
> > > >>> Please vote:
> > > >>> +1 move to git
> > > >>> 0 don’t care
> > > >>> -1 stay on svn
> > > >>>
> > > >>> +1.
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > >
> > >
> >
>
Re: VOTE: move to git
Posted by Jimmy Xiang <jx...@cloudera.com>.
+1
On Wed, Apr 15, 2015 at 3:09 PM, Vivek Shrivastava <vivshrivastava@gmail.com
> wrote:
> +1
> On Apr 15, 2015 6:06 PM, "Vaibhav Gumashta" <vg...@hortonworks.com>
> wrote:
>
> > +1
> >
> > On 4/15/15, 2:55 PM, "Prasanth Jayachandran"
> > <pj...@hortonworks.com> wrote:
> >
> > >+1
> > >
> > >> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <go...@apache.org>
> > >>wrote:
> > >>
> > >> +1
> > >>
> > >> End the merge madness.
> > >>
> > >> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
> > >>
> > >>> Hi.
> > >>> We’ve been discussing this some time ago; this time I¹d like to start
> > >>>an
> > >>> official vote about moving Hive project to git from svn.
> > >>>
> > >>> I volunteer to facilitate the move; that seems to be just filing
> INFRA
> > >>> jira, and following instructions such as verifying that the new repo
> is
> > >>> sane.
> > >>>
> > >>> Please vote:
> > >>> +1 move to git
> > >>> 0 don’t care
> > >>> -1 stay on svn
> > >>>
> > >>> +1.
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >
> >
> >
>
Re: VOTE: move to git
Posted by Vivek Shrivastava <vi...@gmail.com>.
+1
On Apr 15, 2015 6:06 PM, "Vaibhav Gumashta" <vg...@hortonworks.com>
wrote:
> +1
>
> On 4/15/15, 2:55 PM, "Prasanth Jayachandran"
> <pj...@hortonworks.com> wrote:
>
> >+1
> >
> >> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <go...@apache.org>
> >>wrote:
> >>
> >> +1
> >>
> >> End the merge madness.
> >>
> >> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
> >>
> >>> Hi.
> >>> We’ve been discussing this some time ago; this time I¹d like to start
> >>>an
> >>> official vote about moving Hive project to git from svn.
> >>>
> >>> I volunteer to facilitate the move; that seems to be just filing INFRA
> >>> jira, and following instructions such as verifying that the new repo is
> >>> sane.
> >>>
> >>> Please vote:
> >>> +1 move to git
> >>> 0 don’t care
> >>> -1 stay on svn
> >>>
> >>> +1.
> >>>
> >>>
> >>>
> >>
> >>
> >
>
>
Re: VOTE: move to git
Posted by Vaibhav Gumashta <vg...@hortonworks.com>.
+1
On 4/15/15, 2:55 PM, "Prasanth Jayachandran"
<pj...@hortonworks.com> wrote:
>+1
>
>> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <go...@apache.org>
>>wrote:
>>
>> +1
>>
>> End the merge madness.
>>
>> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
>>
>>> Hi.
>>> We’ve been discussing this some time ago; this time I¹d like to start
>>>an
>>> official vote about moving Hive project to git from svn.
>>>
>>> I volunteer to facilitate the move; that seems to be just filing INFRA
>>> jira, and following instructions such as verifying that the new repo is
>>> sane.
>>>
>>> Please vote:
>>> +1 move to git
>>> 0 don’t care
>>> -1 stay on svn
>>>
>>> +1.
>>>
>>>
>>>
>>
>>
>
Re: VOTE: move to git
Posted by Prasanth Jayachandran <pj...@hortonworks.com>.
+1
> On Apr 15, 2015, at 2:48 PM, Gopal Vijayaraghavan <go...@apache.org> wrote:
>
> +1
>
> End the merge madness.
>
> On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
>
>> Hi.
>> We’ve been discussing this some time ago; this time I¹d like to start an
>> official vote about moving Hive project to git from svn.
>>
>> I volunteer to facilitate the move; that seems to be just filing INFRA
>> jira, and following instructions such as verifying that the new repo is
>> sane.
>>
>> Please vote:
>> +1 move to git
>> 0 don’t care
>> -1 stay on svn
>>
>> +1.
>>
>>
>>
>
>
Re: VOTE: move to git
Posted by Gopal Vijayaraghavan <go...@apache.org>.
+1
End the merge madness.
On 4/15/15, 11:46 PM, "Sergey Shelukhin" <se...@apache.org> wrote:
>Hi.
>We’ve been discussing this some time ago; this time I¹d like to start an
>official vote about moving Hive project to git from svn.
>
>I volunteer to facilitate the move; that seems to be just filing INFRA
>jira, and following instructions such as verifying that the new repo is
>sane.
>
>Please vote:
>+1 move to git
>0 don’t care
>-1 stay on svn
>
>+1.
>
>
>
Re: VOTE: move to git
Posted by Chao Sun <ch...@cloudera.com>.
+1. Looking forward to seeing it get implemented.
On Thu, Apr 16, 2015 at 12:11 AM, Owen O'Malley <ow...@gmail.com>
wrote:
> +1
>
> Thanks for taking the initiative and starting this.
>
> .. Owen
>
> > On Apr 15, 2015, at 23:46, Sergey Shelukhin <se...@apache.org> wrote:
> >
> > Hi.
> > We’ve been discussing this some time ago; this time I¹d like to start an
> > official vote about moving Hive project to git from svn.
> >
> > I volunteer to facilitate the move; that seems to be just filing INFRA
> > jira, and following instructions such as verifying that the new repo is
> > sane.
> >
> > Please vote:
> > +1 move to git
> > 0 don’t care
> > -1 stay on svn
> >
> > +1.
> >
> >
> >
>
--
Best,
Chao
Re: VOTE: move to git
Posted by Owen O'Malley <ow...@gmail.com>.
+1
Thanks for taking the initiative and starting this.
.. Owen
> On Apr 15, 2015, at 23:46, Sergey Shelukhin <se...@apache.org> wrote:
>
> Hi.
> We’ve been discussing this some time ago; this time I¹d like to start an
> official vote about moving Hive project to git from svn.
>
> I volunteer to facilitate the move; that seems to be just filing INFRA
> jira, and following instructions such as verifying that the new repo is
> sane.
>
> Please vote:
> +1 move to git
> 0 don’t care
> -1 stay on svn
>
> +1.
>
>
>
Re: VOTE: move to git
Posted by Lefty Leverenz <le...@gmail.com>.
I'm all for clarity. Git makes me nervous, but I'm sure I'll get used to
it with a little help from my friends.
The wiki would need to be updated by someone who knows more about git than
I do. Ignoring some contributor meeting minutes, "svn" occurs in 14 Hive
wiki pages
<https://cwiki.apache.org/confluence/dosearchsite.action?queryString=svn&where=Hive&type=page&startIndex=0>.
Make that 13 because we can ignore PhabricatorCodeReview
<https://cwiki.apache.org/confluence/display/Hive/PhabricatorCodeReview>.
-- Lefty
On Wed, Apr 15, 2015 at 7:59 PM, Thejas Nair <th...@gmail.com> wrote:
> We need to be clear on how the process works with move to git, I am
> not familiar with the process followed by other groups that use git
> currently.
>
> A [DISCUSS] thread for discussing the specifics might be appropriate.
> I assume the central git repository would still be the one in apache.
> Does that we mean we work using *github* pull requests like what spark
> does ? -
> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingCode
>
> I haven't done this, but I assume it is possible to pull a github pull
> request into the apache git. Would that be the way to merge the patch
> in ?
> One (misplaced?) concern I have about git, is that merging pull
> requests would result in lots of branches and it would be hard to
> understand the sequence of changes. (maybe rebasing the changes in
> pull request before commit would help).
>
> I would like to see more clarity on this before we move ahead.
>
>
> On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
> wrote:
> > Hi.
> > We’ve been discussing this some time ago; this time I¹d like to start an
> > official vote about moving Hive project to git from svn.
> >
> > I volunteer to facilitate the move; that seems to be just filing INFRA
> > jira, and following instructions such as verifying that the new repo is
> > sane.
> >
> > Please vote:
> > +1 move to git
> > 0 don’t care
> > -1 stay on svn
> >
> > +1.
> >
> >
> >
>
Re: VOTE: move to git
Posted by Lefty Leverenz <le...@gmail.com>.
I opened HIVE-10486 <https://issues.apache.org/jira/browse/HIVE-10486> "Update
wiki for switch from svn to git" and listed all the wikidocs that need
revision.
-- Lefty
On Mon, Apr 20, 2015 at 7:22 PM, Sergey Shelukhin <se...@hortonworks.com>
wrote:
> INFRA jira has been filed:
> https://issues.apache.org/jira/browse/INFRA-9488
>
>
> On 15/4/16, 17:38, "Vikram Dixit" <vi...@hortonworks.com> wrote:
>
> >+1. Hope to see this happen soon.
> >
> >On 4/16/15, 11:42 AM, "Sergey Shelukhin" <se...@hortonworks.com> wrote:
> >
> >>It’s hard to tell from bylaws how long this vote should run. I’d say 3
> >>days (release vote length) should be appropriate. After ~51 more hours
> >>(on
> >>Monday) I will file JIRA with INFRA if the consensus stands.
> >>
> >>On 15/4/15, 23:08, "Thejas Nair" <th...@gmail.com> wrote:
> >>
> >>>Thanks Sergey, that's an useful link.
> >>>From there, I found the reference to the accumulo git process guide,
> >>>that looks like a great starting point for hive as well -
> >>>http://accumulo.apache.org/git.html .
> >>>
> >>>We could use some of the suggestions there to make the git history
> >>>saner. For example, do a rebase of the pull request before merging, or
> >>>do a 'merge --squash'. We should create a copy of that in hive wiki.
> >>>
> >>>+1 to the move to git. A big plus is also that we won't need to
> >>>separately create review board entries.
> >>>
> >>>
> >>>
> >>>
> >>>On Wed, Apr 15, 2015 at 6:21 PM, Sergey Shelukhin
> >>><se...@hortonworks.com> wrote:
> >>>> The example process can be viewed here:
> >>>> https://issues.apache.org/jira/browse/INFRA-7768
> >>>>
> >>>> I assume we will use commits and not pull requests.
> >>>>
> >>>> On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
> >>>>
> >>>>>We need to be clear on how the process works with move to git, I am
> >>>>>not familiar with the process followed by other groups that use git
> >>>>>currently.
> >>>>>
> >>>>>A [DISCUSS] thread for discussing the specifics might be appropriate.
> >>>>>I assume the central git repository would still be the one in apache.
> >>>>>Does that we mean we work using *github* pull requests like what spark
> >>>>>does ? -
> >>>>>
> https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spar
> >>>>>k
> >>>>>#
> >>>>>Co
> >>>>>ntributingtoSpark-ContributingCode
> >>>>>
> >>>>>I haven't done this, but I assume it is possible to pull a github pull
> >>>>>request into the apache git. Would that be the way to merge the patch
> >>>>>in ?
> >>>>>One (misplaced?) concern I have about git, is that merging pull
> >>>>>requests would result in lots of branches and it would be hard to
> >>>>>understand the sequence of changes. (maybe rebasing the changes in
> >>>>>pull request before commit would help).
> >>>>>
> >>>>>I would like to see more clarity on this before we move ahead.
> >>>>>
> >>>>>
> >>>>>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
> >>>>>wrote:
> >>>>>> Hi.
> >>>>>> We’ve been discussing this some time ago; this time I¹d like to
> >>>>>>start
> >>>>>>an
> >>>>>> official vote about moving Hive project to git from svn.
> >>>>>>
> >>>>>> I volunteer to facilitate the move; that seems to be just filing
> >>>>>>INFRA
> >>>>>> jira, and following instructions such as verifying that the new repo
> >>>>>>is
> >>>>>> sane.
> >>>>>>
> >>>>>> Please vote:
> >>>>>> +1 move to git
> >>>>>> 0 don’t care
> >>>>>> -1 stay on svn
> >>>>>>
> >>>>>> +1.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>
> >
>
>
Re: VOTE: move to git
Posted by Sergey Shelukhin <se...@hortonworks.com>.
INFRA jira has been filed:
https://issues.apache.org/jira/browse/INFRA-9488
On 15/4/16, 17:38, "Vikram Dixit" <vi...@hortonworks.com> wrote:
>+1. Hope to see this happen soon.
>
>On 4/16/15, 11:42 AM, "Sergey Shelukhin" <se...@hortonworks.com> wrote:
>
>>It’s hard to tell from bylaws how long this vote should run. I’d say 3
>>days (release vote length) should be appropriate. After ~51 more hours
>>(on
>>Monday) I will file JIRA with INFRA if the consensus stands.
>>
>>On 15/4/15, 23:08, "Thejas Nair" <th...@gmail.com> wrote:
>>
>>>Thanks Sergey, that's an useful link.
>>>From there, I found the reference to the accumulo git process guide,
>>>that looks like a great starting point for hive as well -
>>>http://accumulo.apache.org/git.html .
>>>
>>>We could use some of the suggestions there to make the git history
>>>saner. For example, do a rebase of the pull request before merging, or
>>>do a 'merge --squash'. We should create a copy of that in hive wiki.
>>>
>>>+1 to the move to git. A big plus is also that we won't need to
>>>separately create review board entries.
>>>
>>>
>>>
>>>
>>>On Wed, Apr 15, 2015 at 6:21 PM, Sergey Shelukhin
>>><se...@hortonworks.com> wrote:
>>>> The example process can be viewed here:
>>>> https://issues.apache.org/jira/browse/INFRA-7768
>>>>
>>>> I assume we will use commits and not pull requests.
>>>>
>>>> On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
>>>>
>>>>>We need to be clear on how the process works with move to git, I am
>>>>>not familiar with the process followed by other groups that use git
>>>>>currently.
>>>>>
>>>>>A [DISCUSS] thread for discussing the specifics might be appropriate.
>>>>>I assume the central git repository would still be the one in apache.
>>>>>Does that we mean we work using *github* pull requests like what spark
>>>>>does ? -
>>>>>https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spar
>>>>>k
>>>>>#
>>>>>Co
>>>>>ntributingtoSpark-ContributingCode
>>>>>
>>>>>I haven't done this, but I assume it is possible to pull a github pull
>>>>>request into the apache git. Would that be the way to merge the patch
>>>>>in ?
>>>>>One (misplaced?) concern I have about git, is that merging pull
>>>>>requests would result in lots of branches and it would be hard to
>>>>>understand the sequence of changes. (maybe rebasing the changes in
>>>>>pull request before commit would help).
>>>>>
>>>>>I would like to see more clarity on this before we move ahead.
>>>>>
>>>>>
>>>>>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
>>>>>wrote:
>>>>>> Hi.
>>>>>> We’ve been discussing this some time ago; this time I¹d like to
>>>>>>start
>>>>>>an
>>>>>> official vote about moving Hive project to git from svn.
>>>>>>
>>>>>> I volunteer to facilitate the move; that seems to be just filing
>>>>>>INFRA
>>>>>> jira, and following instructions such as verifying that the new repo
>>>>>>is
>>>>>> sane.
>>>>>>
>>>>>> Please vote:
>>>>>> +1 move to git
>>>>>> 0 don’t care
>>>>>> -1 stay on svn
>>>>>>
>>>>>> +1.
>>>>>>
>>>>>>
>>>>>>
>>>>
>>
>
Re: VOTE: move to git
Posted by Vikram Dixit <vi...@hortonworks.com>.
+1. Hope to see this happen soon.
On 4/16/15, 11:42 AM, "Sergey Shelukhin" <se...@hortonworks.com> wrote:
>It’s hard to tell from bylaws how long this vote should run. I’d say 3
>days (release vote length) should be appropriate. After ~51 more hours (on
>Monday) I will file JIRA with INFRA if the consensus stands.
>
>On 15/4/15, 23:08, "Thejas Nair" <th...@gmail.com> wrote:
>
>>Thanks Sergey, that's an useful link.
>>From there, I found the reference to the accumulo git process guide,
>>that looks like a great starting point for hive as well -
>>http://accumulo.apache.org/git.html .
>>
>>We could use some of the suggestions there to make the git history
>>saner. For example, do a rebase of the pull request before merging, or
>>do a 'merge --squash'. We should create a copy of that in hive wiki.
>>
>>+1 to the move to git. A big plus is also that we won't need to
>>separately create review board entries.
>>
>>
>>
>>
>>On Wed, Apr 15, 2015 at 6:21 PM, Sergey Shelukhin
>><se...@hortonworks.com> wrote:
>>> The example process can be viewed here:
>>> https://issues.apache.org/jira/browse/INFRA-7768
>>>
>>> I assume we will use commits and not pull requests.
>>>
>>> On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
>>>
>>>>We need to be clear on how the process works with move to git, I am
>>>>not familiar with the process followed by other groups that use git
>>>>currently.
>>>>
>>>>A [DISCUSS] thread for discussing the specifics might be appropriate.
>>>>I assume the central git repository would still be the one in apache.
>>>>Does that we mean we work using *github* pull requests like what spark
>>>>does ? -
>>>>https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
>>>>#
>>>>Co
>>>>ntributingtoSpark-ContributingCode
>>>>
>>>>I haven't done this, but I assume it is possible to pull a github pull
>>>>request into the apache git. Would that be the way to merge the patch
>>>>in ?
>>>>One (misplaced?) concern I have about git, is that merging pull
>>>>requests would result in lots of branches and it would be hard to
>>>>understand the sequence of changes. (maybe rebasing the changes in
>>>>pull request before commit would help).
>>>>
>>>>I would like to see more clarity on this before we move ahead.
>>>>
>>>>
>>>>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
>>>>wrote:
>>>>> Hi.
>>>>> We’ve been discussing this some time ago; this time I¹d like to start
>>>>>an
>>>>> official vote about moving Hive project to git from svn.
>>>>>
>>>>> I volunteer to facilitate the move; that seems to be just filing
>>>>>INFRA
>>>>> jira, and following instructions such as verifying that the new repo
>>>>>is
>>>>> sane.
>>>>>
>>>>> Please vote:
>>>>> +1 move to git
>>>>> 0 don’t care
>>>>> -1 stay on svn
>>>>>
>>>>> +1.
>>>>>
>>>>>
>>>>>
>>>
>
Re: VOTE: move to git
Posted by Sergey Shelukhin <se...@hortonworks.com>.
It’s hard to tell from bylaws how long this vote should run. I’d say 3
days (release vote length) should be appropriate. After ~51 more hours (on
Monday) I will file JIRA with INFRA if the consensus stands.
On 15/4/15, 23:08, "Thejas Nair" <th...@gmail.com> wrote:
>Thanks Sergey, that's an useful link.
>From there, I found the reference to the accumulo git process guide,
>that looks like a great starting point for hive as well -
>http://accumulo.apache.org/git.html .
>
>We could use some of the suggestions there to make the git history
>saner. For example, do a rebase of the pull request before merging, or
>do a 'merge --squash'. We should create a copy of that in hive wiki.
>
>+1 to the move to git. A big plus is also that we won't need to
>separately create review board entries.
>
>
>
>
>On Wed, Apr 15, 2015 at 6:21 PM, Sergey Shelukhin
><se...@hortonworks.com> wrote:
>> The example process can be viewed here:
>> https://issues.apache.org/jira/browse/INFRA-7768
>>
>> I assume we will use commits and not pull requests.
>>
>> On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
>>
>>>We need to be clear on how the process works with move to git, I am
>>>not familiar with the process followed by other groups that use git
>>>currently.
>>>
>>>A [DISCUSS] thread for discussing the specifics might be appropriate.
>>>I assume the central git repository would still be the one in apache.
>>>Does that we mean we work using *github* pull requests like what spark
>>>does ? -
>>>https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#
>>>Co
>>>ntributingtoSpark-ContributingCode
>>>
>>>I haven't done this, but I assume it is possible to pull a github pull
>>>request into the apache git. Would that be the way to merge the patch
>>>in ?
>>>One (misplaced?) concern I have about git, is that merging pull
>>>requests would result in lots of branches and it would be hard to
>>>understand the sequence of changes. (maybe rebasing the changes in
>>>pull request before commit would help).
>>>
>>>I would like to see more clarity on this before we move ahead.
>>>
>>>
>>>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
>>>wrote:
>>>> Hi.
>>>> We’ve been discussing this some time ago; this time I¹d like to start
>>>>an
>>>> official vote about moving Hive project to git from svn.
>>>>
>>>> I volunteer to facilitate the move; that seems to be just filing INFRA
>>>> jira, and following instructions such as verifying that the new repo
>>>>is
>>>> sane.
>>>>
>>>> Please vote:
>>>> +1 move to git
>>>> 0 don’t care
>>>> -1 stay on svn
>>>>
>>>> +1.
>>>>
>>>>
>>>>
>>
Re: VOTE: move to git
Posted by Thejas Nair <th...@gmail.com>.
Thanks Sergey, that's an useful link.
>From there, I found the reference to the accumulo git process guide,
that looks like a great starting point for hive as well -
http://accumulo.apache.org/git.html .
We could use some of the suggestions there to make the git history
saner. For example, do a rebase of the pull request before merging, or
do a 'merge --squash'. We should create a copy of that in hive wiki.
+1 to the move to git. A big plus is also that we won't need to
separately create review board entries.
On Wed, Apr 15, 2015 at 6:21 PM, Sergey Shelukhin
<se...@hortonworks.com> wrote:
> The example process can be viewed here:
> https://issues.apache.org/jira/browse/INFRA-7768
>
> I assume we will use commits and not pull requests.
>
> On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
>
>>We need to be clear on how the process works with move to git, I am
>>not familiar with the process followed by other groups that use git
>>currently.
>>
>>A [DISCUSS] thread for discussing the specifics might be appropriate.
>>I assume the central git repository would still be the one in apache.
>>Does that we mean we work using *github* pull requests like what spark
>>does ? -
>>https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#Co
>>ntributingtoSpark-ContributingCode
>>
>>I haven't done this, but I assume it is possible to pull a github pull
>>request into the apache git. Would that be the way to merge the patch
>>in ?
>>One (misplaced?) concern I have about git, is that merging pull
>>requests would result in lots of branches and it would be hard to
>>understand the sequence of changes. (maybe rebasing the changes in
>>pull request before commit would help).
>>
>>I would like to see more clarity on this before we move ahead.
>>
>>
>>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
>>wrote:
>>> Hi.
>>> We’ve been discussing this some time ago; this time I¹d like to start an
>>> official vote about moving Hive project to git from svn.
>>>
>>> I volunteer to facilitate the move; that seems to be just filing INFRA
>>> jira, and following instructions such as verifying that the new repo is
>>> sane.
>>>
>>> Please vote:
>>> +1 move to git
>>> 0 don’t care
>>> -1 stay on svn
>>>
>>> +1.
>>>
>>>
>>>
>
Re: VOTE: move to git
Posted by Sergey Shelukhin <se...@hortonworks.com>.
The example process can be viewed here:
https://issues.apache.org/jira/browse/INFRA-7768
I assume we will use commits and not pull requests.
On 15/4/15, 16:59, "Thejas Nair" <th...@gmail.com> wrote:
>We need to be clear on how the process works with move to git, I am
>not familiar with the process followed by other groups that use git
>currently.
>
>A [DISCUSS] thread for discussing the specifics might be appropriate.
>I assume the central git repository would still be the one in apache.
>Does that we mean we work using *github* pull requests like what spark
>does ? -
>https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#Co
>ntributingtoSpark-ContributingCode
>
>I haven't done this, but I assume it is possible to pull a github pull
>request into the apache git. Would that be the way to merge the patch
>in ?
>One (misplaced?) concern I have about git, is that merging pull
>requests would result in lots of branches and it would be hard to
>understand the sequence of changes. (maybe rebasing the changes in
>pull request before commit would help).
>
>I would like to see more clarity on this before we move ahead.
>
>
>On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org>
>wrote:
>> Hi.
>> We’ve been discussing this some time ago; this time I¹d like to start an
>> official vote about moving Hive project to git from svn.
>>
>> I volunteer to facilitate the move; that seems to be just filing INFRA
>> jira, and following instructions such as verifying that the new repo is
>> sane.
>>
>> Please vote:
>> +1 move to git
>> 0 don’t care
>> -1 stay on svn
>>
>> +1.
>>
>>
>>
Re: VOTE: move to git
Posted by Thejas Nair <th...@gmail.com>.
We need to be clear on how the process works with move to git, I am
not familiar with the process followed by other groups that use git
currently.
A [DISCUSS] thread for discussing the specifics might be appropriate.
I assume the central git repository would still be the one in apache.
Does that we mean we work using *github* pull requests like what spark
does ? - https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingCode
I haven't done this, but I assume it is possible to pull a github pull
request into the apache git. Would that be the way to merge the patch
in ?
One (misplaced?) concern I have about git, is that merging pull
requests would result in lots of branches and it would be hard to
understand the sequence of changes. (maybe rebasing the changes in
pull request before commit would help).
I would like to see more clarity on this before we move ahead.
On Wed, Apr 15, 2015 at 2:46 PM, Sergey Shelukhin <se...@apache.org> wrote:
> Hi.
> We’ve been discussing this some time ago; this time I¹d like to start an
> official vote about moving Hive project to git from svn.
>
> I volunteer to facilitate the move; that seems to be just filing INFRA
> jira, and following instructions such as verifying that the new repo is
> sane.
>
> Please vote:
> +1 move to git
> 0 don’t care
> -1 stay on svn
>
> +1.
>
>
>