Re: Git Migration
>>>
>>>>> INFRA-7801 is now complete. all apache-github PR functionality is now
>>>>> enabled.
>>>>>
>>>>> note that (as far as i understand) cannot merge PRs directly into
>> github
>>>>> mirror (since it is a mirror and thus read-only). We will have to
> merge
>>>> PRs
>>>>> into git-wip-us as described here [2] "merging locally" and here [3]
>>>>>
>>>>> Note that [3] also applicable to github PR #. I.e. when we merge, it
> is
>>>>> enough just to metnion "fixes #" to close the PR on the mirror as
>>>> well.
>>>>>
>>>>> If we don't want to merge a PR ("won't fix resolution") we'd have to
>> just
>>>>> close it on github (I think one has to be a part of "apache"
>> organization
>>>>> in github, i suggest to request membership for those who haven't yet
>> done
>>>>> so).
>>>>>
>>>>> Suggested reading
>>>>> [1] https://help.github.com/articles/using-pull-requests Some people
>>>>> asked how to create github pull requests
>>>>> [2] https://help.github.com/articles/merging-a-pull-request see
>> "merging
>>>>> locally"
>>>>> [3]
>>
> https://help.github.com/articles/closing-issues-via-commit-messagescommit
>>>>> messages
>>>>>
>>>>>
>>>>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >>>> wrote:
>>>>>
>>>>>> Asking INFRA to enable related github integration features, filed
>>>>>> as INFRA-7801
>>>>>>
>>>>>>
>>>>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov <
> dlie...@gmail.com
>>>>> wrote:
>>>>>>
>>>>>>> Aha! apache/mahout github mirror is up!
>>>>>>>
>>>>>>> let me try and see if i can do and manage a PR there.
>>>>>>>
>>>>>>> I guess i will still need to file another infra Jira for
>> jira/mailing
>>>>>>> list integration features ( we already voted for that in bulk).
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov <
>> dlie...@gmail.com
>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> (1) git migration of the project is now complete. Any volunteers to
>>>>>>>> verify per INFRA-? If you do, please report back to the issue.
>>>>>>>>
>>>>>>>> (2) Anybody knows what to do with jenkins now? i still don't have
>>>>>>>> proper privileges on it. thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: Git Migration
r as i understand) cannot merge PRs directly into
> > github
> >>>> mirror (since it is a mirror and thus read-only). We will have to
> merge
> >>> PRs
> >>>> into git-wip-us as described here [2] "merging locally" and here [3]
> >>>>
> >>>> Note that [3] also applicable to github PR #. I.e. when we merge, it
> is
> >>>> enough just to metnion "fixes #" to close the PR on the mirror as
> >>> well.
> >>>>
> >>>> If we don't want to merge a PR ("won't fix resolution") we'd have to
> > just
> >>>> close it on github (I think one has to be a part of "apache"
> > organization
> >>>> in github, i suggest to request membership for those who haven't yet
> > done
> >>>> so).
> >>>>
> >>>> Suggested reading
> >>>> [1] https://help.github.com/articles/using-pull-requests Some people
> >>>> asked how to create github pull requests
> >>>> [2] https://help.github.com/articles/merging-a-pull-request see
> > "merging
> >>>> locally"
> >>>> [3]
> >
> https://help.github.com/articles/closing-issues-via-commit-messagescommit
> >>>> messages
> >>>>
> >>>>
> >>>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >>>> wrote:
> >>>>
> >>>>> Asking INFRA to enable related github integration features, filed
> >>>>> as INFRA-7801
> >>>>>
> >>>>>
> >>>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov <
> dlie...@gmail.com
> >>>> wrote:
> >>>>>
> >>>>>> Aha! apache/mahout github mirror is up!
> >>>>>>
> >>>>>> let me try and see if i can do and manage a PR there.
> >>>>>>
> >>>>>> I guess i will still need to file another infra Jira for
> > jira/mailing
> >>>>>> list integration features ( we already voted for that in bulk).
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov <
> > dlie...@gmail.com
> >>>> wrote:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> (1) git migration of the project is now complete. Any volunteers to
> >>>>>>> verify per INFRA-? If you do, please report back to the issue.
> >>>>>>>
> >>>>>>> (2) Anybody knows what to do with jenkins now? i still don't have
> >>>>>>> proper privileges on it. thanks.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> [1] https://issues.apache.org/jira/browse/INFRA-
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
>
>
Re: Git Migration
est membership for those who haven't yet > done >>>> so). >>>> >>>> Suggested reading >>>> [1] https://help.github.com/articles/using-pull-requests Some people >>>> asked how to create github pull requests >>>> [2] https://help.github.com/articles/merging-a-pull-request see > "merging >>>> locally" >>>> [3] > https://help.github.com/articles/closing-issues-via-commit-messagescommit >>>> messages >>>> >>>> >>>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >>> wrote: >>>> >>>>> Asking INFRA to enable related github integration features, filed >>>>> as INFRA-7801 >>>>> >>>>> >>>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov >>> wrote: >>>>> >>>>>> Aha! apache/mahout github mirror is up! >>>>>> >>>>>> let me try and see if i can do and manage a PR there. >>>>>> >>>>>> I guess i will still need to file another infra Jira for > jira/mailing >>>>>> list integration features ( we already voted for that in bulk). >>>>>> >>>>>> >>>>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov < > dlie...@gmail.com >>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> (1) git migration of the project is now complete. Any volunteers to >>>>>>> verify per INFRA-? If you do, please report back to the issue. >>>>>>> >>>>>>> (2) Anybody knows what to do with jenkins now? i still don't have >>>>>>> proper privileges on it. thanks. >>>>>>> >>>>>>> >>>>>>> >>>>>>> [1] https://issues.apache.org/jira/browse/INFRA- >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> >> > >
Re: Git Migration
ome people > >>> asked how to create github pull requests > >>> [2] https://help.github.com/articles/merging-a-pull-request see > "merging > >>> locally" > >>> [3] > https://help.github.com/articles/closing-issues-via-commit-messagescommit > >>> messages > >>> > >>> > >>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >>> wrote: > >>> > >>>> Asking INFRA to enable related github integration features, filed > >>>> as INFRA-7801 > >>>> > >>>> > >>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov >>> wrote: > >>>> > >>>>> Aha! apache/mahout github mirror is up! > >>>>> > >>>>> let me try and see if i can do and manage a PR there. > >>>>> > >>>>> I guess i will still need to file another infra Jira for > jira/mailing > >>>>> list integration features ( we already voted for that in bulk). > >>>>> > >>>>> > >>>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov < > dlie...@gmail.com > >>> wrote: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> (1) git migration of the project is now complete. Any volunteers to > >>>>>> verify per INFRA-? If you do, please report back to the issue. > >>>>>> > >>>>>> (2) Anybody knows what to do with jenkins now? i still don't have > >>>>>> proper privileges on it. thanks. > >>>>>> > >>>>>> > >>>>>> > >>>>>> [1] https://issues.apache.org/jira/browse/INFRA- > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >> > >> > > > >
Re: Git Migration
rticles/merging-a-pull-request see > "merging > >>> locally" > >>> [3] > https://help.github.com/articles/closing-issues-via-commit-messagescommit > >>> messages > >>> > >>> > >>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >>> wrote: > >>> > >>>> Asking INFRA to enable related github integration features, filed > >>>> as INFRA-7801 > >>>> > >>>> > >>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov >>> wrote: > >>>> > >>>>> Aha! apache/mahout github mirror is up! > >>>>> > >>>>> let me try and see if i can do and manage a PR there. > >>>>> > >>>>> I guess i will still need to file another infra Jira for > jira/mailing > >>>>> list integration features ( we already voted for that in bulk). > >>>>> > >>>>> > >>>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov < > dlie...@gmail.com > >>> wrote: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> (1) git migration of the project is now complete. Any volunteers to > >>>>>> verify per INFRA-? If you do, please report back to the issue. > >>>>>> > >>>>>> (2) Anybody knows what to do with jenkins now? i still don't have > >>>>>> proper privileges on it. thanks. > >>>>>> > >>>>>> > >>>>>> > >>>>>> [1] https://issues.apache.org/jira/browse/INFRA- > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >> > >> > > > >
Re: Git Migration
Is there really no way to switch to github as the primary and git.wp as a
mirror? Are we doing this integration like Spark? This would do away with the
two local repos problem (and several extra steps), handle the notifications,
and give us a shiny green button :-) This would also make it easier on
contributors who would like to hit the shiny green button but can’t.
It looks to me like every dev needs to have two repos locally, why not change
the mirror so there is just one local repo, our own, with the upstream set to
github’s apache/mahout
To do this committers would have to be granted write access to github
apache/mahout and git.wp would be read only.
Unless I’m missing something, which is always possible. Has anyone actually
done this yet? Am I wrong about the process?
On May 27, 2014, at 8:19 PM, Pat Ferrel wrote:
>
> On May 26, 2014, at 12:14 AM, Ted Dunning wrote:
>
> With git you can push or pull to multiple repos.
Yes, of course. So we are just pulling a branch from our github remote to our
git-wip local then pushing that to git-wip remote. We need two local repos to
do this. And for adding our own code a PR is unnecessary.
>
> To merge the pull request, you can pull from a specific branch from a
> specific source repo where the pull request came from. Then you push to
> git-wip at apache making sure that the Fixes #... message is on the merge.
> Then magic intervenes and all is well.
If the notification comes to @dev that’s clear.
>
> The nice thing is that most of the commands are visible on the pull request
> itself.
>
> Notifications about pull requests are via email and now that D has
> oh-so-quickly gotten Jake to enable that we should see those on the dev
> list. My guess is that the easiest path would be to create a JIRA wrapper,
> do the merge, push, resolve the JIRA all in one quick session. Not quite
> as easy as the green button, but not heinous.
>
>
>
> On Sun, May 25, 2014 at 11:13 AM, Pat Ferrel wrote:
>
>> I’m confused about the workflow.
>>
>> It looks like you keep two local repos one pointed to your fork on github,
>> the other to git-wip-us. Do your work on your repo (set git-wip-us as
>> upstream to get updates) and when you want to merge do “git request-pull
>> branch url-to-git-wip-us". This will package an uber patch from your repo
>> and communicate with the destination server (I assume). But how do you
>> receive the notification and respond?
>>
>> I’ve never responded to a PR outside of Github, and there was no
>> notification that the PR had been issued outside of the Github UI.
>>
>> On May 25, 2014, at 10:24 AM, Dmitriy Lyubimov wrote:
>>
>> jeninkins: mahout-nightly seems to be running ok off new git.
>> can't get mahout-quality to run thru still. it was failing in execution of
>> Jenkins findBugs publishing plugin, i've desabled this plugin for the time
>> being. Still however couldn't get it run once successfully so far.
>>
>>
>> On Sun, May 25, 2014 at 9:40 AM, Dmitriy Lyubimov
>> wrote:
>>
>>> INFRA-7801 is now complete. all apache-github PR functionality is now
>>> enabled.
>>>
>>> note that (as far as i understand) cannot merge PRs directly into github
>>> mirror (since it is a mirror and thus read-only). We will have to merge
>> PRs
>>> into git-wip-us as described here [2] "merging locally" and here [3]
>>>
>>> Note that [3] also applicable to github PR #. I.e. when we merge, it is
>>> enough just to metnion "fixes #" to close the PR on the mirror as
>> well.
>>>
>>> If we don't want to merge a PR ("won't fix resolution") we'd have to just
>>> close it on github (I think one has to be a part of "apache" organization
>>> in github, i suggest to request membership for those who haven't yet done
>>> so).
>>>
>>> Suggested reading
>>> [1] https://help.github.com/articles/using-pull-requests Some people
>>> asked how to create github pull requests
>>> [2] https://help.github.com/articles/merging-a-pull-request see "merging
>>> locally"
>>> [3]
>>> https://help.github.com/articles/closing-issues-via-commit-messagescommit
>>> messages
>>>
>>>
>>> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >> wrote:
>>>
>>>> Asking INFRA to enable related github integration features, filed
>>>> as INFRA-7801
>>>>
>>>>
>>>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov >> wrote:
>>>>
>&g
Re: Git Migration
Some committers appear not to have their full name set (as it was with svn) : https://git-wip-us.apache.org/repos/asf?p=mahout.git. In some cases, the email is also not the apache handle... I'd suggest to make sure your full name and email are set correctly in your local git before pushing/committing.. at least it was the standard with svn commits.
Re: Git Migration
With git you can push or pull to multiple repos.
To merge the pull request, you can pull from a specific branch from a
specific source repo where the pull request came from. Then you push to
git-wip at apache making sure that the Fixes #... message is on the merge.
Then magic intervenes and all is well.
The nice thing is that most of the commands are visible on the pull request
itself.
Notifications about pull requests are via email and now that D has
oh-so-quickly gotten Jake to enable that we should see those on the dev
list. My guess is that the easiest path would be to create a JIRA wrapper,
do the merge, push, resolve the JIRA all in one quick session. Not quite
as easy as the green button, but not heinous.
On Sun, May 25, 2014 at 11:13 AM, Pat Ferrel wrote:
> I’m confused about the workflow.
>
> It looks like you keep two local repos one pointed to your fork on github,
> the other to git-wip-us. Do your work on your repo (set git-wip-us as
> upstream to get updates) and when you want to merge do “git request-pull
> branch url-to-git-wip-us". This will package an uber patch from your repo
> and communicate with the destination server (I assume). But how do you
> receive the notification and respond?
>
> I’ve never responded to a PR outside of Github, and there was no
> notification that the PR had been issued outside of the Github UI.
>
> On May 25, 2014, at 10:24 AM, Dmitriy Lyubimov wrote:
>
> jeninkins: mahout-nightly seems to be running ok off new git.
> can't get mahout-quality to run thru still. it was failing in execution of
> Jenkins findBugs publishing plugin, i've desabled this plugin for the time
> being. Still however couldn't get it run once successfully so far.
>
>
> On Sun, May 25, 2014 at 9:40 AM, Dmitriy Lyubimov
> wrote:
>
> > INFRA-7801 is now complete. all apache-github PR functionality is now
> > enabled.
> >
> > note that (as far as i understand) cannot merge PRs directly into github
> > mirror (since it is a mirror and thus read-only). We will have to merge
> PRs
> > into git-wip-us as described here [2] "merging locally" and here [3]
> >
> > Note that [3] also applicable to github PR #. I.e. when we merge, it is
> > enough just to metnion "fixes #" to close the PR on the mirror as
> well.
> >
> > If we don't want to merge a PR ("won't fix resolution") we'd have to just
> > close it on github (I think one has to be a part of "apache" organization
> > in github, i suggest to request membership for those who haven't yet done
> > so).
> >
> > Suggested reading
> > [1] https://help.github.com/articles/using-pull-requests Some people
> > asked how to create github pull requests
> > [2] https://help.github.com/articles/merging-a-pull-request see "merging
> > locally"
> > [3]
> > https://help.github.com/articles/closing-issues-via-commit-messagescommit
> > messages
> >
> >
> > On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov >wrote:
> >
> >> Asking INFRA to enable related github integration features, filed
> >> as INFRA-7801
> >>
> >>
> >> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov >wrote:
> >>
> >>> Aha! apache/mahout github mirror is up!
> >>>
> >>> let me try and see if i can do and manage a PR there.
> >>>
> >>> I guess i will still need to file another infra Jira for jira/mailing
> >>> list integration features ( we already voted for that in bulk).
> >>>
> >>>
> >>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov >wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> (1) git migration of the project is now complete. Any volunteers to
> >>>> verify per INFRA-? If you do, please report back to the issue.
> >>>>
> >>>> (2) Anybody knows what to do with jenkins now? i still don't have
> >>>> proper privileges on it. thanks.
> >>>>
> >>>>
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/INFRA-
> >>>>
> >>>
> >>>
> >>
> >
>
>
Re: Git Migration
I’m confused about the workflow.
It looks like you keep two local repos one pointed to your fork on github, the
other to git-wip-us. Do your work on your repo (set git-wip-us as upstream to
get updates) and when you want to merge do “git request-pull branch
url-to-git-wip-us". This will package an uber patch from your repo and
communicate with the destination server (I assume). But how do you receive the
notification and respond?
I’ve never responded to a PR outside of Github, and there was no notification
that the PR had been issued outside of the Github UI.
On May 25, 2014, at 10:24 AM, Dmitriy Lyubimov wrote:
jeninkins: mahout-nightly seems to be running ok off new git.
can't get mahout-quality to run thru still. it was failing in execution of
Jenkins findBugs publishing plugin, i've desabled this plugin for the time
being. Still however couldn't get it run once successfully so far.
On Sun, May 25, 2014 at 9:40 AM, Dmitriy Lyubimov wrote:
> INFRA-7801 is now complete. all apache-github PR functionality is now
> enabled.
>
> note that (as far as i understand) cannot merge PRs directly into github
> mirror (since it is a mirror and thus read-only). We will have to merge PRs
> into git-wip-us as described here [2] "merging locally" and here [3]
>
> Note that [3] also applicable to github PR #. I.e. when we merge, it is
> enough just to metnion "fixes #" to close the PR on the mirror as well.
>
> If we don't want to merge a PR ("won't fix resolution") we'd have to just
> close it on github (I think one has to be a part of "apache" organization
> in github, i suggest to request membership for those who haven't yet done
> so).
>
> Suggested reading
> [1] https://help.github.com/articles/using-pull-requests Some people
> asked how to create github pull requests
> [2] https://help.github.com/articles/merging-a-pull-request see "merging
> locally"
> [3] https://help.github.com/articles/closing-issues-via-commit-messages commit
> messages
>
>
> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov wrote:
>
>> Asking INFRA to enable related github integration features, filed
>> as INFRA-7801
>>
>>
>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov wrote:
>>
>>> Aha! apache/mahout github mirror is up!
>>>
>>> let me try and see if i can do and manage a PR there.
>>>
>>> I guess i will still need to file another infra Jira for jira/mailing
>>> list integration features ( we already voted for that in bulk).
>>>
>>>
>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote:
>>>
>>>> Hi,
>>>>
>>>> (1) git migration of the project is now complete. Any volunteers to
>>>> verify per INFRA-? If you do, please report back to the issue.
>>>>
>>>> (2) Anybody knows what to do with jenkins now? i still don't have
>>>> proper privileges on it. thanks.
>>>>
>>>>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-
>>>>
>>>
>>>
>>
>
Re: Git Migration
jeninkins: mahout-nightly seems to be running ok off new git.
can't get mahout-quality to run thru still. it was failing in execution of
Jenkins findBugs publishing plugin, i've desabled this plugin for the time
being. Still however couldn't get it run once successfully so far.
On Sun, May 25, 2014 at 9:40 AM, Dmitriy Lyubimov wrote:
> INFRA-7801 is now complete. all apache-github PR functionality is now
> enabled.
>
> note that (as far as i understand) cannot merge PRs directly into github
> mirror (since it is a mirror and thus read-only). We will have to merge PRs
> into git-wip-us as described here [2] "merging locally" and here [3]
>
> Note that [3] also applicable to github PR #. I.e. when we merge, it is
> enough just to metnion "fixes #" to close the PR on the mirror as well.
>
> If we don't want to merge a PR ("won't fix resolution") we'd have to just
> close it on github (I think one has to be a part of "apache" organization
> in github, i suggest to request membership for those who haven't yet done
> so).
>
> Suggested reading
> [1] https://help.github.com/articles/using-pull-requests Some people
> asked how to create github pull requests
> [2] https://help.github.com/articles/merging-a-pull-request see "merging
> locally"
> [3] https://help.github.com/articles/closing-issues-via-commit-messages commit
> messages
>
>
> On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov wrote:
>
>> Asking INFRA to enable related github integration features, filed
>> as INFRA-7801
>>
>>
>> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov wrote:
>>
>>> Aha! apache/mahout github mirror is up!
>>>
>>> let me try and see if i can do and manage a PR there.
>>>
>>> I guess i will still need to file another infra Jira for jira/mailing
>>> list integration features ( we already voted for that in bulk).
>>>
>>>
>>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote:
>>>
>>>> Hi,
>>>>
>>>> (1) git migration of the project is now complete. Any volunteers to
>>>> verify per INFRA-? If you do, please report back to the issue.
>>>>
>>>> (2) Anybody knows what to do with jenkins now? i still don't have
>>>> proper privileges on it. thanks.
>>>>
>>>>
>>>>
>>>> [1] https://issues.apache.org/jira/browse/INFRA-
>>>>
>>>
>>>
>>
>
Re: Git Migration
INFRA-7801 is now complete. all apache-github PR functionality is now
enabled.
note that (as far as i understand) cannot merge PRs directly into github
mirror (since it is a mirror and thus read-only). We will have to merge PRs
into git-wip-us as described here [2] "merging locally" and here [3]
Note that [3] also applicable to github PR #. I.e. when we merge, it is
enough just to metnion "fixes #" to close the PR on the mirror as well.
If we don't want to merge a PR ("won't fix resolution") we'd have to just
close it on github (I think one has to be a part of "apache" organization
in github, i suggest to request membership for those who haven't yet done
so).
Suggested reading
[1] https://help.github.com/articles/using-pull-requests Some people asked
how to create github pull requests
[2] https://help.github.com/articles/merging-a-pull-request see "merging
locally"
[3] https://help.github.com/articles/closing-issues-via-commit-messages commit
messages
On Fri, May 23, 2014 at 12:31 PM, Dmitriy Lyubimov wrote:
> Asking INFRA to enable related github integration features, filed
> as INFRA-7801
>
>
> On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov wrote:
>
>> Aha! apache/mahout github mirror is up!
>>
>> let me try and see if i can do and manage a PR there.
>>
>> I guess i will still need to file another infra Jira for jira/mailing
>> list integration features ( we already voted for that in bulk).
>>
>>
>> On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote:
>>
>>> Hi,
>>>
>>> (1) git migration of the project is now complete. Any volunteers to
>>> verify per INFRA-? If you do, please report back to the issue.
>>>
>>> (2) Anybody knows what to do with jenkins now? i still don't have proper
>>> privileges on it. thanks.
>>>
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-
>>>
>>
>>
>
Re: Git Migration
Asking INFRA to enable related github integration features, filed as INFRA-7801 On Fri, May 23, 2014 at 10:42 AM, Dmitriy Lyubimov wrote: > Aha! apache/mahout github mirror is up! > > let me try and see if i can do and manage a PR there. > > I guess i will still need to file another infra Jira for jira/mailing > list integration features ( we already voted for that in bulk). > > > On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote: > >> Hi, >> >> (1) git migration of the project is now complete. Any volunteers to >> verify per INFRA-? If you do, please report back to the issue. >> >> (2) Anybody knows what to do with jenkins now? i still don't have proper >> privileges on it. thanks. >> >> >> >> [1] https://issues.apache.org/jira/browse/INFRA- >> > >
Re: Git Migration
Aha! apache/mahout github mirror is up! let me try and see if i can do and manage a PR there. I guess i will still need to file another infra Jira for jira/mailing list integration features ( we already voted for that in bulk). On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote: > Hi, > > (1) git migration of the project is now complete. Any volunteers to verify > per INFRA-? If you do, please report back to the issue. > > (2) Anybody knows what to do with jenkins now? i still don't have proper > privileges on it. thanks. > > > > [1] https://issues.apache.org/jira/browse/INFRA- >
Re: Git Migration
I will check as soon as I can. That won't be soon since I am currently on a plane stuck by weather in the wrong place. No idea when I will able to touch the internet again. Sent from my iPhone > On May 22, 2014, at 13:55, Dmitriy Lyubimov wrote: > > At this point I simply would like everyone to verify they can push commits > to master branch of git-wp-us.a.o per instructions in INFRA- and report > back there (I can push).
Re: Git Migration
Wow. Quick We also need web site updates quickly. Sent from my iPhone > On May 22, 2014, at 13:14, Dmitriy Lyubimov wrote: > > Hi, > > (1) git migration of the project is now complete. Any volunteers to verify > per INFRA-? If you do, please report back to the issue. > > (2) Anybody knows what to do with jenkins now? i still don't have proper > privileges on it. thanks. > > > > [1] https://issues.apache.org/jira/browse/INFRA-
Re: Git Migration
Works for me. Shannon On 5/22/14, 3:45 PM, Gokhan Capan wrote: Works for me as well Gokhan On Thu, May 22, 2014 at 9:23 PM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: Thanks; I just pushed successfully. On Thu, May 22, 2014 at 10:55 AM, Dmitriy Lyubimov wrote: did you read Jake's email earlier at dev/infra discussion? he describes and makes references here. It is two-fold: first we can push whatever commits to master of https://git-wip-us.apache.org/repos/asf?p=mahout.git However the other side of the coin is that significant commits should go thru pull requests directly to (if i understand it correctly) apache/mahout mirror on github. Such pull requests are managed thru commits to git-wp as well by specific messages (again, see references in Jake's email). My understanding is that github integration features are not yet enabled, only commits to master of git-wp-us.a.o are at this point. At this point I simply would like everyone to verify they can push commits to master branch of git-wp-us.a.o per instructions in INFRA- and report back there (I can push). I guess someone (perhaps me) will have to write the manual for working with github pull requests (mainly, merging them to git-wp-us.o.a and closing them). On Thu, May 22, 2014 at 10:47 AM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: What's the workflow to commit a change? I'm totally in the dark about that. On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote: Hi, (1) git migration of the project is now complete. Any volunteers to verify per INFRA-? If you do, please report back to the issue. (2) Anybody knows what to do with jenkins now? i still don't have proper privileges on it. thanks. [1] https://issues.apache.org/jira/browse/INFRA-
Re: Git Migration
working on Quality build, it is still failing for the moment. On Thu, May 22, 2014 at 1:15 PM, Dmitriy Lyubimov wrote: > updated Jenkins nightly build. build succeeded. >
Re: Git Migration
updated Jenkins nightly build. build succeeded.
Re: Git Migration
Works for me as well Gokhan On Thu, May 22, 2014 at 9:23 PM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: > Thanks; I just pushed successfully. > > > On Thu, May 22, 2014 at 10:55 AM, Dmitriy Lyubimov >wrote: > > > did you read Jake's email earlier at dev/infra discussion? he describes > and > > makes references here. > > > > It is two-fold: first we can push whatever commits to master of > > https://git-wip-us.apache.org/repos/asf?p=mahout.git > > > > However the other side of the coin is that significant commits should go > > thru pull requests directly to (if i understand it correctly) > apache/mahout > > mirror on github. Such pull requests are managed thru commits to git-wp > as > > well by specific messages (again, see references in Jake's email). My > > understanding is that github integration features are not yet enabled, > only > > commits to master of git-wp-us.a.o are at this point. > > > > At this point I simply would like everyone to verify they can push > commits > > to master branch of git-wp-us.a.o per instructions in INFRA- and > report > > back there (I can push). > > > > I guess someone (perhaps me) will have to write the manual for working > with > > github pull requests (mainly, merging them to git-wp-us.o.a and closing > > them). > > > > > > On Thu, May 22, 2014 at 10:47 AM, Andrew Musselman < > > andrew.mussel...@gmail.com> wrote: > > > > > What's the workflow to commit a change? I'm totally in the dark about > > > that. > > > > > > > > > On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov > > >wrote: > > > > > > > Hi, > > > > > > > > (1) git migration of the project is now complete. Any volunteers to > > > verify > > > > per INFRA-? If you do, please report back to the issue. > > > > > > > > (2) Anybody knows what to do with jenkins now? i still don't have > > proper > > > > privileges on it. thanks. > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA- > > > > > > > > > >
Re: Git Migration
Thanks; I just pushed successfully. On Thu, May 22, 2014 at 10:55 AM, Dmitriy Lyubimov wrote: > did you read Jake's email earlier at dev/infra discussion? he describes and > makes references here. > > It is two-fold: first we can push whatever commits to master of > https://git-wip-us.apache.org/repos/asf?p=mahout.git > > However the other side of the coin is that significant commits should go > thru pull requests directly to (if i understand it correctly) apache/mahout > mirror on github. Such pull requests are managed thru commits to git-wp as > well by specific messages (again, see references in Jake's email). My > understanding is that github integration features are not yet enabled, only > commits to master of git-wp-us.a.o are at this point. > > At this point I simply would like everyone to verify they can push commits > to master branch of git-wp-us.a.o per instructions in INFRA- and report > back there (I can push). > > I guess someone (perhaps me) will have to write the manual for working with > github pull requests (mainly, merging them to git-wp-us.o.a and closing > them). > > > On Thu, May 22, 2014 at 10:47 AM, Andrew Musselman < > andrew.mussel...@gmail.com> wrote: > > > What's the workflow to commit a change? I'm totally in the dark about > > that. > > > > > > On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov > >wrote: > > > > > Hi, > > > > > > (1) git migration of the project is now complete. Any volunteers to > > verify > > > per INFRA-? If you do, please report back to the issue. > > > > > > (2) Anybody knows what to do with jenkins now? i still don't have > proper > > > privileges on it. thanks. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA- > > > > > >
Re: Git Migration
did you read Jake's email earlier at dev/infra discussion? he describes and makes references here. It is two-fold: first we can push whatever commits to master of https://git-wip-us.apache.org/repos/asf?p=mahout.git However the other side of the coin is that significant commits should go thru pull requests directly to (if i understand it correctly) apache/mahout mirror on github. Such pull requests are managed thru commits to git-wp as well by specific messages (again, see references in Jake's email). My understanding is that github integration features are not yet enabled, only commits to master of git-wp-us.a.o are at this point. At this point I simply would like everyone to verify they can push commits to master branch of git-wp-us.a.o per instructions in INFRA- and report back there (I can push). I guess someone (perhaps me) will have to write the manual for working with github pull requests (mainly, merging them to git-wp-us.o.a and closing them). On Thu, May 22, 2014 at 10:47 AM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: > What's the workflow to commit a change? I'm totally in the dark about > that. > > > On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov >wrote: > > > Hi, > > > > (1) git migration of the project is now complete. Any volunteers to > verify > > per INFRA-? If you do, please report back to the issue. > > > > (2) Anybody knows what to do with jenkins now? i still don't have proper > > privileges on it. thanks. > > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA- > > >
Re: Git Migration
What's the workflow to commit a change? I'm totally in the dark about that. On Thu, May 22, 2014 at 10:14 AM, Dmitriy Lyubimov wrote: > Hi, > > (1) git migration of the project is now complete. Any volunteers to verify > per INFRA-? If you do, please report back to the issue. > > (2) Anybody knows what to do with jenkins now? i still don't have proper > privileges on it. thanks. > > > > [1] https://issues.apache.org/jira/browse/INFRA- >
Git Migration
Hi, (1) git migration of the project is now complete. Any volunteers to verify per INFRA-? If you do, please report back to the issue. (2) Anybody knows what to do with jenkins now? i still don't have proper privileges on it. thanks. [1] https://issues.apache.org/jira/browse/INFRA-
