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 <ser...@hortonworks.com> wrote: > INFRA jira has been filed: > https://issues.apache.org/jira/browse/INFRA-9488 > > > On 15/4/16, 17:38, "Vikram Dixit" <vik...@hortonworks.com> wrote: > > >+1. Hope to see this happen soon. > > > >On 4/16/15, 11:42 AM, "Sergey Shelukhin" <ser...@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" <thejas.n...@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 > >>><ser...@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" <thejas.n...@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 <ser...@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. > >>>>>> > >>>>>> > >>>>>> > >>>> > >> > > > >
