You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2013/10/25 18:45:58 UTC
DISCUSSION: Move to GIT?
At yesterday's dev meetup -- minutes to follow -- it was suggested we move
the project to git as our repo of truth.
What do folks think? How patches are contributed and committer will have
to change to match git-flow.
Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
kind enough to write up the steps involved moving their project over. See
the discussion on how they come up w/ a process in particular.
St.Ack
---------- Forwarded message ----------
From: Josh Elser <jo...@gmail.com>
Date: Fri, Oct 25, 2013 at 12:25 AM
Subject: Accumulo's transition to git
To: Stack <st...@duboce.net>
Stack,
As promised, here's the info that I had collected when Accumulo made the
transition from SVN to Git.
Make sure you have some mailing list consensus, and then open up an INFRA
ticket. For us, we requested the following things
1. Specify which SVN branches you want in Git, and if you want them
renamed. Also, which you want the default Git branch to be on clone.
2. If you have any contribs, specify which other SVN path you want as their
own Git repos.
3. Specify the format of the subject for the git commit notifications email
and to which mailing list.
4. Request update of mirroring on git.a.o and github.com/apache/...
5. Transition from svn2jira to git2jira (honestly, I don't remember what
this was anymore.. maybe commenting on Jira for issue mentions in commits)
6. Request delivery of pull-requests to a given mailing list.
7. Request update reviewboard to the new repo.
Our INFRA ticket can be found at [1]
FWIW, we also had a huge discussion about how we were going to use Git so
that we didn't constantly duplicate a bunch of commits cherry-picking
changes everywhere. There was a bunch of teaching we had to do to make sure
we had a good commit history and could still use features like git-bisect.
The result of that is at [2].
Joe Stein also sent us Kafka's use of Git that was helpful when writing
down how users should contribute patches. [3]
I hope all this helps! Despite the pain we went through in getting this all
set up (dealing with coordination of INFRA to lock the SVN repos, transfer
to Git, verify accuracy, and people who then didn't know how to use Git), I
think everyone is happy we did it.
- Josh
[1] https://issues.apache.org/**jira/browse/INFRA-6392<https://issues.apache.org/jira/browse/INFRA-6392>
[2] http://accumulo.apache.org/**git.html<http://accumulo.apache.org/git.html>
[3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
[4] https://git-wip-us.apache.org/
Re: DISCUSSION: Move to GIT?
Posted by Gary Helmling <gh...@gmail.com>.
+1!!!
On Fri, Oct 25, 2013 at 10:12 AM, Ted Yu <yu...@gmail.com> wrote:
> +1 too.
>
>
> On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <jesse.k.yates@gmail.com
> >wrote:
>
> > +1
> >
> > Do all my work in git anyways :)
> >
> > On Friday, October 25, 2013, Stack wrote:
> >
> > > At yesterday's dev meetup -- minutes to follow -- it was suggested we
> > move
> > > the project to git as our repo of truth.
> > >
> > > What do folks think? How patches are contributed and committer will
> have
> > > to change to match git-flow.
> > >
> > > Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
> > was
> > > kind enough to write up the steps involved moving their project over.
> > See
> > > the discussion on how they come up w/ a process in particular.
> > >
> > > St.Ack
> > >
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > Subject: Accumulo's transition to git
> > > To: Stack <stack@duboce.net <javascript:;>>
> > >
> > >
> > > Stack,
> > >
> > > As promised, here's the info that I had collected when Accumulo made
> the
> > > transition from SVN to Git.
> > >
> > > Make sure you have some mailing list consensus, and then open up an
> INFRA
> > > ticket. For us, we requested the following things
> > >
> > > 1. Specify which SVN branches you want in Git, and if you want them
> > > renamed. Also, which you want the default Git branch to be on clone.
> > >
> > > 2. If you have any contribs, specify which other SVN path you want as
> > their
> > > own Git repos.
> > >
> > > 3. Specify the format of the subject for the git commit notifications
> > email
> > > and to which mailing list.
> > >
> > > 4. Request update of mirroring on git.a.o and github.com/apache/...
> > >
> > > 5. Transition from svn2jira to git2jira (honestly, I don't remember
> what
> > > this was anymore.. maybe commenting on Jira for issue mentions in
> > commits)
> > >
> > > 6. Request delivery of pull-requests to a given mailing list.
> > >
> > > 7. Request update reviewboard to the new repo.
> > >
> > > Our INFRA ticket can be found at [1]
> > >
> > > FWIW, we also had a huge discussion about how we were going to use Git
> so
> > > that we didn't constantly duplicate a bunch of commits cherry-picking
> > > changes everywhere. There was a bunch of teaching we had to do to make
> > sure
> > > we had a good commit history and could still use features like
> > git-bisect.
> > > The result of that is at [2].
> > >
> > > Joe Stein also sent us Kafka's use of Git that was helpful when writing
> > > down how users should contribute patches. [3]
> > >
> > > I hope all this helps! Despite the pain we went through in getting this
> > all
> > > set up (dealing with coordination of INFRA to lock the SVN repos,
> > transfer
> > > to Git, verify accuracy, and people who then didn't know how to use
> > Git), I
> > > think everyone is happy we did it.
> > >
> > > - Josh
> > >
> > > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > https://issues.apache.org/jira/browse/INFRA-6392>
> > > [2] http://accumulo.apache.org/**git.html<
> > > http://accumulo.apache.org/git.html>
> > > [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow
> <
> > > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > [4] https://git-wip-us.apache.org/
> > >
> >
> >
> > --
> > -------------------
> > Jesse Yates
> > @jesse_yates
> > jyates.github.com
> >
>
Re: DISCUSSION: Move to GIT?
Posted by Ted Yu <yu...@gmail.com>.
That's my understanding - keeping Hadoop QA integration.
On Oct 25, 2013, at 11:41 AM, Nicolas Liochon <nk...@gmail.com> wrote:
> I don't really care. I will follow.
>
> I suppose we will keep our integration with JIRA, so we will have to submit
> a patch anyway to get it validated by pre-commit stuff?
>
> Nicolas
>
>
>
> On Fri, Oct 25, 2013 at 8:30 PM, Sergey Shelukhin <se...@hortonworks.com>wrote:
>
>> +1, also only use svn to commit
>>
>>
>> On Fri, Oct 25, 2013 at 11:10 AM, Enis Söztutar <en...@apache.org> wrote:
>>
>>> +1000.
>>>
>>> Enis
>>>
>>>
>>> On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com>
>> wrote:
>>>
>>>> +1. I've actually only used SVN to commit patches.
>>>>
>>>> I'd suggest we maintain the same commit style (straight line rebased
>>>> commits per release branch, branches off trunk for major features)
>> after
>>>> the move to git as opposed to the github style (lots of branch/merges).
>>>>
>>>> Jon.
>>>>
>>>>
>>>> On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org>
>>> wrote:
>>>>
>>>>> +1 I've actually been using git to do most of my work lately.
>>>>>
>>>>>
>>>>> On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
>>>>>
>>>>>> git is more powerful and flexible.
>>>>>>
>>>>>> 2013/10/26 Ted Yu <yu...@gmail.com>:
>>>>>>> +1 too.
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
>>>> jesse.k.yates@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Do all my work in git anyways :)
>>>>>>>>
>>>>>>>> On Friday, October 25, 2013, Stack wrote:
>>>>>>>>
>>>>>>>>> At yesterday's dev meetup -- minutes to follow -- it was
>>> suggested
>>>>> we
>>>>>>>> move
>>>>>>>>> the project to git as our repo of truth.
>>>>>>>>>
>>>>>>>>> What do folks think? How patches are contributed and
>> committer
>>>> will
>>>>>> have
>>>>>>>>> to change to match git-flow.
>>>>>>>>>
>>>>>>>>> Josh Eiser, an accumulo committer, was at the dev meetup
>>> yesterday
>>>>> and
>>>>>>>> was
>>>>>>>>> kind enough to write up the steps involved moving their
>> project
>>>>> over.
>>>>>>>> See
>>>>>>>>> the discussion on how they come up w/ a process in particular.
>>>>>>>>>
>>>>>>>>> St.Ack
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------- Forwarded message ----------
>>>>>>>>> From: Josh Elser <josh.elser@gmail.com <javascript:;>>
>>>>>>>>> Date: Fri, Oct 25, 2013 at 12:25 AM
>>>>>>>>> Subject: Accumulo's transition to git
>>>>>>>>> To: Stack <stack@duboce.net <javascript:;>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Stack,
>>>>>>>>>
>>>>>>>>> As promised, here's the info that I had collected when
>> Accumulo
>>>> made
>>>>>> the
>>>>>>>>> transition from SVN to Git.
>>>>>>>>>
>>>>>>>>> Make sure you have some mailing list consensus, and then open
>> up
>>>> an
>>>>>> INFRA
>>>>>>>>> ticket. For us, we requested the following things
>>>>>>>>>
>>>>>>>>> 1. Specify which SVN branches you want in Git, and if you want
>>>> them
>>>>>>>>> renamed. Also, which you want the default Git branch to be on
>>>> clone.
>>>>>>>>>
>>>>>>>>> 2. If you have any contribs, specify which other SVN path you
>>> want
>>>>> as
>>>>>>>> their
>>>>>>>>> own Git repos.
>>>>>>>>>
>>>>>>>>> 3. Specify the format of the subject for the git commit
>>>>> notifications
>>>>>>>> email
>>>>>>>>> and to which mailing list.
>>>>>>>>>
>>>>>>>>> 4. Request update of mirroring on git.a.o and
>>> github.com/apache/.
>>>> ..
>>>>>>>>>
>>>>>>>>> 5. Transition from svn2jira to git2jira (honestly, I don't
>>>> remember
>>>>>> what
>>>>>>>>> this was anymore.. maybe commenting on Jira for issue mentions
>>> in
>>>>>>>> commits)
>>>>>>>>>
>>>>>>>>> 6. Request delivery of pull-requests to a given mailing list.
>>>>>>>>>
>>>>>>>>> 7. Request update reviewboard to the new repo.
>>>>>>>>>
>>>>>>>>> Our INFRA ticket can be found at [1]
>>>>>>>>>
>>>>>>>>> FWIW, we also had a huge discussion about how we were going to
>>> use
>>>>>> Git so
>>>>>>>>> that we didn't constantly duplicate a bunch of commits
>>>>> cherry-picking
>>>>>>>>> changes everywhere. There was a bunch of teaching we had to do
>>> to
>>>>> make
>>>>>>>> sure
>>>>>>>>> we had a good commit history and could still use features like
>>>>>>>> git-bisect.
>>>>>>>>> The result of that is at [2].
>>>>>>>>>
>>>>>>>>> Joe Stein also sent us Kafka's use of Git that was helpful
>> when
>>>>>> writing
>>>>>>>>> down how users should contribute patches. [3]
>>>>>>>>>
>>>>>>>>> I hope all this helps! Despite the pain we went through in
>>> getting
>>>>>> this
>>>>>>>> all
>>>>>>>>> set up (dealing with coordination of INFRA to lock the SVN
>>> repos,
>>>>>>>> transfer
>>>>>>>>> to Git, verify accuracy, and people who then didn't know how
>> to
>>>> use
>>>>>>>> Git), I
>>>>>>>>> think everyone is happy we did it.
>>>>>>>>>
>>>>>>>>> - Josh
>>>>>>>>>
>>>>>>>>> [1] https://issues.apache.org/**jira/browse/INFRA-6392<
>>>>>>>>> https://issues.apache.org/jira/browse/INFRA-6392>
>>>>>>>>> [2] http://accumulo.apache.org/**git.html<
>>>>>>>>> http://accumulo.apache.org/git.html>
>>>>>>>>> [3]
>>>>>> https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow
>> <
>> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
>>>>>>>>> [4] https://git-wip-us.apache.org/
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -------------------
>>>>>>>> Jesse Yates
>>>>>>>> @jesse_yates
>>>>>>>> jyates.github.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best Regards,
>>>>>> Haosdent Huang
>>>>
>>>>
>>>>
>>>> --
>>>> // Jonathan Hsieh (shay)
>>>> // Software Engineer, Cloudera
>>>> // jon@cloudera.com
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
Re: DISCUSSION: Move to GIT?
Posted by Nicolas Liochon <nk...@gmail.com>.
I don't really care. I will follow.
I suppose we will keep our integration with JIRA, so we will have to submit
a patch anyway to get it validated by pre-commit stuff?
Nicolas
On Fri, Oct 25, 2013 at 8:30 PM, Sergey Shelukhin <se...@hortonworks.com>wrote:
> +1, also only use svn to commit
>
>
> On Fri, Oct 25, 2013 at 11:10 AM, Enis Söztutar <en...@apache.org> wrote:
>
> > +1000.
> >
> > Enis
> >
> >
> > On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com>
> wrote:
> >
> > > +1. I've actually only used SVN to commit patches.
> > >
> > > I'd suggest we maintain the same commit style (straight line rebased
> > > commits per release branch, branches off trunk for major features)
> after
> > > the move to git as opposed to the github style (lots of branch/merges).
> > >
> > > Jon.
> > >
> > >
> > > On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org>
> > wrote:
> > >
> > > > +1 I've actually been using git to do most of my work lately.
> > > >
> > > >
> > > > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> > > >
> > > > > git is more powerful and flexible.
> > > > >
> > > > > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > > > > +1 too.
> > > > > >
> > > > > >
> > > > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> > > jesse.k.yates@gmail.com
> > > > > >wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Do all my work in git anyways :)
> > > > > >>
> > > > > >> On Friday, October 25, 2013, Stack wrote:
> > > > > >>
> > > > > >> > At yesterday's dev meetup -- minutes to follow -- it was
> > suggested
> > > > we
> > > > > >> move
> > > > > >> > the project to git as our repo of truth.
> > > > > >> >
> > > > > >> > What do folks think? How patches are contributed and
> committer
> > > will
> > > > > have
> > > > > >> > to change to match git-flow.
> > > > > >> >
> > > > > >> > Josh Eiser, an accumulo committer, was at the dev meetup
> > yesterday
> > > > and
> > > > > >> was
> > > > > >> > kind enough to write up the steps involved moving their
> project
> > > > over.
> > > > > >> See
> > > > > >> > the discussion on how they come up w/ a process in particular.
> > > > > >> >
> > > > > >> > St.Ack
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > ---------- Forwarded message ----------
> > > > > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > > > >> > Subject: Accumulo's transition to git
> > > > > >> > To: Stack <stack@duboce.net <javascript:;>>
> > > > > >> >
> > > > > >> >
> > > > > >> > Stack,
> > > > > >> >
> > > > > >> > As promised, here's the info that I had collected when
> Accumulo
> > > made
> > > > > the
> > > > > >> > transition from SVN to Git.
> > > > > >> >
> > > > > >> > Make sure you have some mailing list consensus, and then open
> up
> > > an
> > > > > INFRA
> > > > > >> > ticket. For us, we requested the following things
> > > > > >> >
> > > > > >> > 1. Specify which SVN branches you want in Git, and if you want
> > > them
> > > > > >> > renamed. Also, which you want the default Git branch to be on
> > > clone.
> > > > > >> >
> > > > > >> > 2. If you have any contribs, specify which other SVN path you
> > want
> > > > as
> > > > > >> their
> > > > > >> > own Git repos.
> > > > > >> >
> > > > > >> > 3. Specify the format of the subject for the git commit
> > > > notifications
> > > > > >> email
> > > > > >> > and to which mailing list.
> > > > > >> >
> > > > > >> > 4. Request update of mirroring on git.a.o and
> > github.com/apache/.
> > > ..
> > > > > >> >
> > > > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> > > remember
> > > > > what
> > > > > >> > this was anymore.. maybe commenting on Jira for issue mentions
> > in
> > > > > >> commits)
> > > > > >> >
> > > > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > > > >> >
> > > > > >> > 7. Request update reviewboard to the new repo.
> > > > > >> >
> > > > > >> > Our INFRA ticket can be found at [1]
> > > > > >> >
> > > > > >> > FWIW, we also had a huge discussion about how we were going to
> > use
> > > > > Git so
> > > > > >> > that we didn't constantly duplicate a bunch of commits
> > > > cherry-picking
> > > > > >> > changes everywhere. There was a bunch of teaching we had to do
> > to
> > > > make
> > > > > >> sure
> > > > > >> > we had a good commit history and could still use features like
> > > > > >> git-bisect.
> > > > > >> > The result of that is at [2].
> > > > > >> >
> > > > > >> > Joe Stein also sent us Kafka's use of Git that was helpful
> when
> > > > > writing
> > > > > >> > down how users should contribute patches. [3]
> > > > > >> >
> > > > > >> > I hope all this helps! Despite the pain we went through in
> > getting
> > > > > this
> > > > > >> all
> > > > > >> > set up (dealing with coordination of INFRA to lock the SVN
> > repos,
> > > > > >> transfer
> > > > > >> > to Git, verify accuracy, and people who then didn't know how
> to
> > > use
> > > > > >> Git), I
> > > > > >> > think everyone is happy we did it.
> > > > > >> >
> > > > > >> > - Josh
> > > > > >> >
> > > > > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > > > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > > > > >> > [2] http://accumulo.apache.org/**git.html<
> > > > > >> > http://accumulo.apache.org/git.html>
> > > > > >> > [3]
> > > > > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow
> <
> > > > > >> >
> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > > > >> > [4] https://git-wip-us.apache.org/
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> -------------------
> > > > > >> Jesse Yates
> > > > > >> @jesse_yates
> > > > > >> jyates.github.com
> > > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Haosdent Huang
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > // Jonathan Hsieh (shay)
> > > // Software Engineer, Cloudera
> > > // jon@cloudera.com
> > >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: DISCUSSION: Move to GIT?
Posted by Stack <st...@duboce.net>.
On Fri, Oct 25, 2013 at 11:42 AM, Enis Söztutar <en...@gmail.com> wrote:
> > I'd suggest we maintain the same commit style (straight line rebased
> commits per release branch, branches off trunk for major features) after
> the move to git as opposed to the github style (lots of branch/merges).
>
> +1 to that as well. Having multiple commits and merge commits per jira will
> complicate commit log digging a lot. And we do not care about a patch's
> individual history.
>
> Will FB guys ok with this? How does this affect 0.89-fb branch.
>
We could leave old branches on svn.
St.Ack
Re: DISCUSSION: Move to GIT?
Posted by Enis Söztutar <en...@gmail.com>.
> I'd suggest we maintain the same commit style (straight line rebased
commits per release branch, branches off trunk for major features) after
the move to git as opposed to the github style (lots of branch/merges).
+1 to that as well. Having multiple commits and merge commits per jira will
complicate commit log digging a lot. And we do not care about a patch's
individual history.
Will FB guys ok with this? How does this affect 0.89-fb branch.
Enis
On Fri, Oct 25, 2013 at 11:30 AM, Sergey Shelukhin
<se...@hortonworks.com>wrote:
> +1, also only use svn to commit
>
>
> On Fri, Oct 25, 2013 at 11:10 AM, Enis Söztutar <en...@apache.org> wrote:
>
> > +1000.
> >
> > Enis
> >
> >
> > On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com>
> wrote:
> >
> > > +1. I've actually only used SVN to commit patches.
> > >
> > > I'd suggest we maintain the same commit style (straight line rebased
> > > commits per release branch, branches off trunk for major features)
> after
> > > the move to git as opposed to the github style (lots of branch/merges).
> > >
> > > Jon.
> > >
> > >
> > > On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org>
> > wrote:
> > >
> > > > +1 I've actually been using git to do most of my work lately.
> > > >
> > > >
> > > > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> > > >
> > > > > git is more powerful and flexible.
> > > > >
> > > > > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > > > > +1 too.
> > > > > >
> > > > > >
> > > > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> > > jesse.k.yates@gmail.com
> > > > > >wrote:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Do all my work in git anyways :)
> > > > > >>
> > > > > >> On Friday, October 25, 2013, Stack wrote:
> > > > > >>
> > > > > >> > At yesterday's dev meetup -- minutes to follow -- it was
> > suggested
> > > > we
> > > > > >> move
> > > > > >> > the project to git as our repo of truth.
> > > > > >> >
> > > > > >> > What do folks think? How patches are contributed and
> committer
> > > will
> > > > > have
> > > > > >> > to change to match git-flow.
> > > > > >> >
> > > > > >> > Josh Eiser, an accumulo committer, was at the dev meetup
> > yesterday
> > > > and
> > > > > >> was
> > > > > >> > kind enough to write up the steps involved moving their
> project
> > > > over.
> > > > > >> See
> > > > > >> > the discussion on how they come up w/ a process in particular.
> > > > > >> >
> > > > > >> > St.Ack
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > ---------- Forwarded message ----------
> > > > > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > > > >> > Subject: Accumulo's transition to git
> > > > > >> > To: Stack <stack@duboce.net <javascript:;>>
> > > > > >> >
> > > > > >> >
> > > > > >> > Stack,
> > > > > >> >
> > > > > >> > As promised, here's the info that I had collected when
> Accumulo
> > > made
> > > > > the
> > > > > >> > transition from SVN to Git.
> > > > > >> >
> > > > > >> > Make sure you have some mailing list consensus, and then open
> up
> > > an
> > > > > INFRA
> > > > > >> > ticket. For us, we requested the following things
> > > > > >> >
> > > > > >> > 1. Specify which SVN branches you want in Git, and if you want
> > > them
> > > > > >> > renamed. Also, which you want the default Git branch to be on
> > > clone.
> > > > > >> >
> > > > > >> > 2. If you have any contribs, specify which other SVN path you
> > want
> > > > as
> > > > > >> their
> > > > > >> > own Git repos.
> > > > > >> >
> > > > > >> > 3. Specify the format of the subject for the git commit
> > > > notifications
> > > > > >> email
> > > > > >> > and to which mailing list.
> > > > > >> >
> > > > > >> > 4. Request update of mirroring on git.a.o and
> > github.com/apache/.
> > > ..
> > > > > >> >
> > > > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> > > remember
> > > > > what
> > > > > >> > this was anymore.. maybe commenting on Jira for issue mentions
> > in
> > > > > >> commits)
> > > > > >> >
> > > > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > > > >> >
> > > > > >> > 7. Request update reviewboard to the new repo.
> > > > > >> >
> > > > > >> > Our INFRA ticket can be found at [1]
> > > > > >> >
> > > > > >> > FWIW, we also had a huge discussion about how we were going to
> > use
> > > > > Git so
> > > > > >> > that we didn't constantly duplicate a bunch of commits
> > > > cherry-picking
> > > > > >> > changes everywhere. There was a bunch of teaching we had to do
> > to
> > > > make
> > > > > >> sure
> > > > > >> > we had a good commit history and could still use features like
> > > > > >> git-bisect.
> > > > > >> > The result of that is at [2].
> > > > > >> >
> > > > > >> > Joe Stein also sent us Kafka's use of Git that was helpful
> when
> > > > > writing
> > > > > >> > down how users should contribute patches. [3]
> > > > > >> >
> > > > > >> > I hope all this helps! Despite the pain we went through in
> > getting
> > > > > this
> > > > > >> all
> > > > > >> > set up (dealing with coordination of INFRA to lock the SVN
> > repos,
> > > > > >> transfer
> > > > > >> > to Git, verify accuracy, and people who then didn't know how
> to
> > > use
> > > > > >> Git), I
> > > > > >> > think everyone is happy we did it.
> > > > > >> >
> > > > > >> > - Josh
> > > > > >> >
> > > > > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > > > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > > > > >> > [2] http://accumulo.apache.org/**git.html<
> > > > > >> > http://accumulo.apache.org/git.html>
> > > > > >> > [3]
> > > > > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow
> <
> > > > > >> >
> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > > > >> > [4] https://git-wip-us.apache.org/
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> -------------------
> > > > > >> Jesse Yates
> > > > > >> @jesse_yates
> > > > > >> jyates.github.com
> > > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Haosdent Huang
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > // Jonathan Hsieh (shay)
> > > // Software Engineer, Cloudera
> > > // jon@cloudera.com
> > >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: DISCUSSION: Move to GIT?
Posted by Sergey Shelukhin <se...@hortonworks.com>.
+1, also only use svn to commit
On Fri, Oct 25, 2013 at 11:10 AM, Enis Söztutar <en...@apache.org> wrote:
> +1000.
>
> Enis
>
>
> On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
>
> > +1. I've actually only used SVN to commit patches.
> >
> > I'd suggest we maintain the same commit style (straight line rebased
> > commits per release branch, branches off trunk for major features) after
> > the move to git as opposed to the github style (lots of branch/merges).
> >
> > Jon.
> >
> >
> > On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org>
> wrote:
> >
> > > +1 I've actually been using git to do most of my work lately.
> > >
> > >
> > > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> > >
> > > > git is more powerful and flexible.
> > > >
> > > > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > > > +1 too.
> > > > >
> > > > >
> > > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> > jesse.k.yates@gmail.com
> > > > >wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> Do all my work in git anyways :)
> > > > >>
> > > > >> On Friday, October 25, 2013, Stack wrote:
> > > > >>
> > > > >> > At yesterday's dev meetup -- minutes to follow -- it was
> suggested
> > > we
> > > > >> move
> > > > >> > the project to git as our repo of truth.
> > > > >> >
> > > > >> > What do folks think? How patches are contributed and committer
> > will
> > > > have
> > > > >> > to change to match git-flow.
> > > > >> >
> > > > >> > Josh Eiser, an accumulo committer, was at the dev meetup
> yesterday
> > > and
> > > > >> was
> > > > >> > kind enough to write up the steps involved moving their project
> > > over.
> > > > >> See
> > > > >> > the discussion on how they come up w/ a process in particular.
> > > > >> >
> > > > >> > St.Ack
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > ---------- Forwarded message ----------
> > > > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > > >> > Subject: Accumulo's transition to git
> > > > >> > To: Stack <stack@duboce.net <javascript:;>>
> > > > >> >
> > > > >> >
> > > > >> > Stack,
> > > > >> >
> > > > >> > As promised, here's the info that I had collected when Accumulo
> > made
> > > > the
> > > > >> > transition from SVN to Git.
> > > > >> >
> > > > >> > Make sure you have some mailing list consensus, and then open up
> > an
> > > > INFRA
> > > > >> > ticket. For us, we requested the following things
> > > > >> >
> > > > >> > 1. Specify which SVN branches you want in Git, and if you want
> > them
> > > > >> > renamed. Also, which you want the default Git branch to be on
> > clone.
> > > > >> >
> > > > >> > 2. If you have any contribs, specify which other SVN path you
> want
> > > as
> > > > >> their
> > > > >> > own Git repos.
> > > > >> >
> > > > >> > 3. Specify the format of the subject for the git commit
> > > notifications
> > > > >> email
> > > > >> > and to which mailing list.
> > > > >> >
> > > > >> > 4. Request update of mirroring on git.a.o and
> github.com/apache/.
> > ..
> > > > >> >
> > > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> > remember
> > > > what
> > > > >> > this was anymore.. maybe commenting on Jira for issue mentions
> in
> > > > >> commits)
> > > > >> >
> > > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > > >> >
> > > > >> > 7. Request update reviewboard to the new repo.
> > > > >> >
> > > > >> > Our INFRA ticket can be found at [1]
> > > > >> >
> > > > >> > FWIW, we also had a huge discussion about how we were going to
> use
> > > > Git so
> > > > >> > that we didn't constantly duplicate a bunch of commits
> > > cherry-picking
> > > > >> > changes everywhere. There was a bunch of teaching we had to do
> to
> > > make
> > > > >> sure
> > > > >> > we had a good commit history and could still use features like
> > > > >> git-bisect.
> > > > >> > The result of that is at [2].
> > > > >> >
> > > > >> > Joe Stein also sent us Kafka's use of Git that was helpful when
> > > > writing
> > > > >> > down how users should contribute patches. [3]
> > > > >> >
> > > > >> > I hope all this helps! Despite the pain we went through in
> getting
> > > > this
> > > > >> all
> > > > >> > set up (dealing with coordination of INFRA to lock the SVN
> repos,
> > > > >> transfer
> > > > >> > to Git, verify accuracy, and people who then didn't know how to
> > use
> > > > >> Git), I
> > > > >> > think everyone is happy we did it.
> > > > >> >
> > > > >> > - Josh
> > > > >> >
> > > > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > > > >> > [2] http://accumulo.apache.org/**git.html<
> > > > >> > http://accumulo.apache.org/git.html>
> > > > >> > [3]
> > > > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > > > >> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > > >> > [4] https://git-wip-us.apache.org/
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> -------------------
> > > > >> Jesse Yates
> > > > >> @jesse_yates
> > > > >> jyates.github.com
> > > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > Haosdent Huang
> > > >
> > >
> >
> >
> >
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // jon@cloudera.com
> >
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: DISCUSSION: Move to GIT?
Posted by Enis Söztutar <en...@apache.org>.
+1000.
Enis
On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
> +1. I've actually only used SVN to commit patches.
>
> I'd suggest we maintain the same commit style (straight line rebased
> commits per release branch, branches off trunk for major features) after
> the move to git as opposed to the github style (lots of branch/merges).
>
> Jon.
>
>
> On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org> wrote:
>
> > +1 I've actually been using git to do most of my work lately.
> >
> >
> > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> >
> > > git is more powerful and flexible.
> > >
> > > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > > +1 too.
> > > >
> > > >
> > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> jesse.k.yates@gmail.com
> > > >wrote:
> > > >
> > > >> +1
> > > >>
> > > >> Do all my work in git anyways :)
> > > >>
> > > >> On Friday, October 25, 2013, Stack wrote:
> > > >>
> > > >> > At yesterday's dev meetup -- minutes to follow -- it was suggested
> > we
> > > >> move
> > > >> > the project to git as our repo of truth.
> > > >> >
> > > >> > What do folks think? How patches are contributed and committer
> will
> > > have
> > > >> > to change to match git-flow.
> > > >> >
> > > >> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday
> > and
> > > >> was
> > > >> > kind enough to write up the steps involved moving their project
> > over.
> > > >> See
> > > >> > the discussion on how they come up w/ a process in particular.
> > > >> >
> > > >> > St.Ack
> > > >> >
> > > >> >
> > > >> >
> > > >> > ---------- Forwarded message ----------
> > > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > >> > Subject: Accumulo's transition to git
> > > >> > To: Stack <stack@duboce.net <javascript:;>>
> > > >> >
> > > >> >
> > > >> > Stack,
> > > >> >
> > > >> > As promised, here's the info that I had collected when Accumulo
> made
> > > the
> > > >> > transition from SVN to Git.
> > > >> >
> > > >> > Make sure you have some mailing list consensus, and then open up
> an
> > > INFRA
> > > >> > ticket. For us, we requested the following things
> > > >> >
> > > >> > 1. Specify which SVN branches you want in Git, and if you want
> them
> > > >> > renamed. Also, which you want the default Git branch to be on
> clone.
> > > >> >
> > > >> > 2. If you have any contribs, specify which other SVN path you want
> > as
> > > >> their
> > > >> > own Git repos.
> > > >> >
> > > >> > 3. Specify the format of the subject for the git commit
> > notifications
> > > >> email
> > > >> > and to which mailing list.
> > > >> >
> > > >> > 4. Request update of mirroring on git.a.o and github.com/apache/.
> ..
> > > >> >
> > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> remember
> > > what
> > > >> > this was anymore.. maybe commenting on Jira for issue mentions in
> > > >> commits)
> > > >> >
> > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > >> >
> > > >> > 7. Request update reviewboard to the new repo.
> > > >> >
> > > >> > Our INFRA ticket can be found at [1]
> > > >> >
> > > >> > FWIW, we also had a huge discussion about how we were going to use
> > > Git so
> > > >> > that we didn't constantly duplicate a bunch of commits
> > cherry-picking
> > > >> > changes everywhere. There was a bunch of teaching we had to do to
> > make
> > > >> sure
> > > >> > we had a good commit history and could still use features like
> > > >> git-bisect.
> > > >> > The result of that is at [2].
> > > >> >
> > > >> > Joe Stein also sent us Kafka's use of Git that was helpful when
> > > writing
> > > >> > down how users should contribute patches. [3]
> > > >> >
> > > >> > I hope all this helps! Despite the pain we went through in getting
> > > this
> > > >> all
> > > >> > set up (dealing with coordination of INFRA to lock the SVN repos,
> > > >> transfer
> > > >> > to Git, verify accuracy, and people who then didn't know how to
> use
> > > >> Git), I
> > > >> > think everyone is happy we did it.
> > > >> >
> > > >> > - Josh
> > > >> >
> > > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > > >> > [2] http://accumulo.apache.org/**git.html<
> > > >> > http://accumulo.apache.org/git.html>
> > > >> > [3]
> > > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > > >> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > >> > [4] https://git-wip-us.apache.org/
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> -------------------
> > > >> Jesse Yates
> > > >> @jesse_yates
> > > >> jyates.github.com
> > > >>
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Haosdent Huang
> > >
> >
>
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // jon@cloudera.com
>
Re: DISCUSSION: Move to GIT?
Posted by Nick Dimiduk <nd...@gmail.com>.
On Fri, Oct 25, 2013 at 10:58 AM, Jonathan Hsieh <jo...@cloudera.com> wrote:
> I'd suggest we maintain the same commit style (straight line rebased
> commits per release branch, branches off trunk for major features) after
> the move to git as opposed to the github style (lots of branch/merges).
>
I also prefer git. I'll second Jon's recommendation here of maintaining a
straight line version history too.
On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org> wrote:
>
> > +1 I've actually been using git to do most of my work lately.
> >
> >
> > On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> >
> > > git is more powerful and flexible.
> > >
> > > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > > +1 too.
> > > >
> > > >
> > > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <
> jesse.k.yates@gmail.com
> > > >wrote:
> > > >
> > > >> +1
> > > >>
> > > >> Do all my work in git anyways :)
> > > >>
> > > >> On Friday, October 25, 2013, Stack wrote:
> > > >>
> > > >> > At yesterday's dev meetup -- minutes to follow -- it was suggested
> > we
> > > >> move
> > > >> > the project to git as our repo of truth.
> > > >> >
> > > >> > What do folks think? How patches are contributed and committer
> will
> > > have
> > > >> > to change to match git-flow.
> > > >> >
> > > >> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday
> > and
> > > >> was
> > > >> > kind enough to write up the steps involved moving their project
> > over.
> > > >> See
> > > >> > the discussion on how they come up w/ a process in particular.
> > > >> >
> > > >> > St.Ack
> > > >> >
> > > >> >
> > > >> >
> > > >> > ---------- Forwarded message ----------
> > > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > > >> > Subject: Accumulo's transition to git
> > > >> > To: Stack <stack@duboce.net <javascript:;>>
> > > >> >
> > > >> >
> > > >> > Stack,
> > > >> >
> > > >> > As promised, here's the info that I had collected when Accumulo
> made
> > > the
> > > >> > transition from SVN to Git.
> > > >> >
> > > >> > Make sure you have some mailing list consensus, and then open up
> an
> > > INFRA
> > > >> > ticket. For us, we requested the following things
> > > >> >
> > > >> > 1. Specify which SVN branches you want in Git, and if you want
> them
> > > >> > renamed. Also, which you want the default Git branch to be on
> clone.
> > > >> >
> > > >> > 2. If you have any contribs, specify which other SVN path you want
> > as
> > > >> their
> > > >> > own Git repos.
> > > >> >
> > > >> > 3. Specify the format of the subject for the git commit
> > notifications
> > > >> email
> > > >> > and to which mailing list.
> > > >> >
> > > >> > 4. Request update of mirroring on git.a.o and github.com/apache/.
> ..
> > > >> >
> > > >> > 5. Transition from svn2jira to git2jira (honestly, I don't
> remember
> > > what
> > > >> > this was anymore.. maybe commenting on Jira for issue mentions in
> > > >> commits)
> > > >> >
> > > >> > 6. Request delivery of pull-requests to a given mailing list.
> > > >> >
> > > >> > 7. Request update reviewboard to the new repo.
> > > >> >
> > > >> > Our INFRA ticket can be found at [1]
> > > >> >
> > > >> > FWIW, we also had a huge discussion about how we were going to use
> > > Git so
> > > >> > that we didn't constantly duplicate a bunch of commits
> > cherry-picking
> > > >> > changes everywhere. There was a bunch of teaching we had to do to
> > make
> > > >> sure
> > > >> > we had a good commit history and could still use features like
> > > >> git-bisect.
> > > >> > The result of that is at [2].
> > > >> >
> > > >> > Joe Stein also sent us Kafka's use of Git that was helpful when
> > > writing
> > > >> > down how users should contribute patches. [3]
> > > >> >
> > > >> > I hope all this helps! Despite the pain we went through in getting
> > > this
> > > >> all
> > > >> > set up (dealing with coordination of INFRA to lock the SVN repos,
> > > >> transfer
> > > >> > to Git, verify accuracy, and people who then didn't know how to
> use
> > > >> Git), I
> > > >> > think everyone is happy we did it.
> > > >> >
> > > >> > - Josh
> > > >> >
> > > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > > >> > [2] http://accumulo.apache.org/**git.html<
> > > >> > http://accumulo.apache.org/git.html>
> > > >> > [3]
> > > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > > >> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > > >> > [4] https://git-wip-us.apache.org/
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> -------------------
> > > >> Jesse Yates
> > > >> @jesse_yates
> > > >> jyates.github.com
> > > >>
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Haosdent Huang
> > >
> >
>
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // jon@cloudera.com
>
Re: DISCUSSION: Move to GIT?
Posted by Jonathan Hsieh <jo...@cloudera.com>.
+1. I've actually only used SVN to commit patches.
I'd suggest we maintain the same commit style (straight line rebased
commits per release branch, branches off trunk for major features) after
the move to git as opposed to the github style (lots of branch/merges).
Jon.
On Fri, Oct 25, 2013 at 10:44 AM, Elliott Clark <ec...@apache.org> wrote:
> +1 I've actually been using git to do most of my work lately.
>
>
> On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
>
> > git is more powerful and flexible.
> >
> > 2013/10/26 Ted Yu <yu...@gmail.com>:
> > > +1 too.
> > >
> > >
> > > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <jesse.k.yates@gmail.com
> > >wrote:
> > >
> > >> +1
> > >>
> > >> Do all my work in git anyways :)
> > >>
> > >> On Friday, October 25, 2013, Stack wrote:
> > >>
> > >> > At yesterday's dev meetup -- minutes to follow -- it was suggested
> we
> > >> move
> > >> > the project to git as our repo of truth.
> > >> >
> > >> > What do folks think? How patches are contributed and committer will
> > have
> > >> > to change to match git-flow.
> > >> >
> > >> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday
> and
> > >> was
> > >> > kind enough to write up the steps involved moving their project
> over.
> > >> See
> > >> > the discussion on how they come up w/ a process in particular.
> > >> >
> > >> > St.Ack
> > >> >
> > >> >
> > >> >
> > >> > ---------- Forwarded message ----------
> > >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > >> > Subject: Accumulo's transition to git
> > >> > To: Stack <stack@duboce.net <javascript:;>>
> > >> >
> > >> >
> > >> > Stack,
> > >> >
> > >> > As promised, here's the info that I had collected when Accumulo made
> > the
> > >> > transition from SVN to Git.
> > >> >
> > >> > Make sure you have some mailing list consensus, and then open up an
> > INFRA
> > >> > ticket. For us, we requested the following things
> > >> >
> > >> > 1. Specify which SVN branches you want in Git, and if you want them
> > >> > renamed. Also, which you want the default Git branch to be on clone.
> > >> >
> > >> > 2. If you have any contribs, specify which other SVN path you want
> as
> > >> their
> > >> > own Git repos.
> > >> >
> > >> > 3. Specify the format of the subject for the git commit
> notifications
> > >> email
> > >> > and to which mailing list.
> > >> >
> > >> > 4. Request update of mirroring on git.a.o and github.com/apache/...
> > >> >
> > >> > 5. Transition from svn2jira to git2jira (honestly, I don't remember
> > what
> > >> > this was anymore.. maybe commenting on Jira for issue mentions in
> > >> commits)
> > >> >
> > >> > 6. Request delivery of pull-requests to a given mailing list.
> > >> >
> > >> > 7. Request update reviewboard to the new repo.
> > >> >
> > >> > Our INFRA ticket can be found at [1]
> > >> >
> > >> > FWIW, we also had a huge discussion about how we were going to use
> > Git so
> > >> > that we didn't constantly duplicate a bunch of commits
> cherry-picking
> > >> > changes everywhere. There was a bunch of teaching we had to do to
> make
> > >> sure
> > >> > we had a good commit history and could still use features like
> > >> git-bisect.
> > >> > The result of that is at [2].
> > >> >
> > >> > Joe Stein also sent us Kafka's use of Git that was helpful when
> > writing
> > >> > down how users should contribute patches. [3]
> > >> >
> > >> > I hope all this helps! Despite the pain we went through in getting
> > this
> > >> all
> > >> > set up (dealing with coordination of INFRA to lock the SVN repos,
> > >> transfer
> > >> > to Git, verify accuracy, and people who then didn't know how to use
> > >> Git), I
> > >> > think everyone is happy we did it.
> > >> >
> > >> > - Josh
> > >> >
> > >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > >> > https://issues.apache.org/jira/browse/INFRA-6392>
> > >> > [2] http://accumulo.apache.org/**git.html<
> > >> > http://accumulo.apache.org/git.html>
> > >> > [3]
> > https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > >> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > >> > [4] https://git-wip-us.apache.org/
> > >> >
> > >>
> > >>
> > >> --
> > >> -------------------
> > >> Jesse Yates
> > >> @jesse_yates
> > >> jyates.github.com
> > >>
> >
> >
> >
> > --
> > Best Regards,
> > Haosdent Huang
> >
>
--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com
Re: DISCUSSION: Move to GIT?
Posted by Elliott Clark <ec...@apache.org>.
+1 I've actually been using git to do most of my work lately.
On Fri, Oct 25, 2013 at 10:16 AM, 黄浩松 <ha...@gmail.com> wrote:
> git is more powerful and flexible.
>
> 2013/10/26 Ted Yu <yu...@gmail.com>:
> > +1 too.
> >
> >
> > On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <jesse.k.yates@gmail.com
> >wrote:
> >
> >> +1
> >>
> >> Do all my work in git anyways :)
> >>
> >> On Friday, October 25, 2013, Stack wrote:
> >>
> >> > At yesterday's dev meetup -- minutes to follow -- it was suggested we
> >> move
> >> > the project to git as our repo of truth.
> >> >
> >> > What do folks think? How patches are contributed and committer will
> have
> >> > to change to match git-flow.
> >> >
> >> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
> >> was
> >> > kind enough to write up the steps involved moving their project over.
> >> See
> >> > the discussion on how they come up w/ a process in particular.
> >> >
> >> > St.Ack
> >> >
> >> >
> >> >
> >> > ---------- Forwarded message ----------
> >> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> >> > Date: Fri, Oct 25, 2013 at 12:25 AM
> >> > Subject: Accumulo's transition to git
> >> > To: Stack <stack@duboce.net <javascript:;>>
> >> >
> >> >
> >> > Stack,
> >> >
> >> > As promised, here's the info that I had collected when Accumulo made
> the
> >> > transition from SVN to Git.
> >> >
> >> > Make sure you have some mailing list consensus, and then open up an
> INFRA
> >> > ticket. For us, we requested the following things
> >> >
> >> > 1. Specify which SVN branches you want in Git, and if you want them
> >> > renamed. Also, which you want the default Git branch to be on clone.
> >> >
> >> > 2. If you have any contribs, specify which other SVN path you want as
> >> their
> >> > own Git repos.
> >> >
> >> > 3. Specify the format of the subject for the git commit notifications
> >> email
> >> > and to which mailing list.
> >> >
> >> > 4. Request update of mirroring on git.a.o and github.com/apache/...
> >> >
> >> > 5. Transition from svn2jira to git2jira (honestly, I don't remember
> what
> >> > this was anymore.. maybe commenting on Jira for issue mentions in
> >> commits)
> >> >
> >> > 6. Request delivery of pull-requests to a given mailing list.
> >> >
> >> > 7. Request update reviewboard to the new repo.
> >> >
> >> > Our INFRA ticket can be found at [1]
> >> >
> >> > FWIW, we also had a huge discussion about how we were going to use
> Git so
> >> > that we didn't constantly duplicate a bunch of commits cherry-picking
> >> > changes everywhere. There was a bunch of teaching we had to do to make
> >> sure
> >> > we had a good commit history and could still use features like
> >> git-bisect.
> >> > The result of that is at [2].
> >> >
> >> > Joe Stein also sent us Kafka's use of Git that was helpful when
> writing
> >> > down how users should contribute patches. [3]
> >> >
> >> > I hope all this helps! Despite the pain we went through in getting
> this
> >> all
> >> > set up (dealing with coordination of INFRA to lock the SVN repos,
> >> transfer
> >> > to Git, verify accuracy, and people who then didn't know how to use
> >> Git), I
> >> > think everyone is happy we did it.
> >> >
> >> > - Josh
> >> >
> >> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> >> > https://issues.apache.org/jira/browse/INFRA-6392>
> >> > [2] http://accumulo.apache.org/**git.html<
> >> > http://accumulo.apache.org/git.html>
> >> > [3]
> https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> >> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> >> > [4] https://git-wip-us.apache.org/
> >> >
> >>
> >>
> >> --
> >> -------------------
> >> Jesse Yates
> >> @jesse_yates
> >> jyates.github.com
> >>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: DISCUSSION: Move to GIT?
Posted by 黄浩松 <ha...@gmail.com>.
git is more powerful and flexible.
2013/10/26 Ted Yu <yu...@gmail.com>:
> +1 too.
>
>
> On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <je...@gmail.com>wrote:
>
>> +1
>>
>> Do all my work in git anyways :)
>>
>> On Friday, October 25, 2013, Stack wrote:
>>
>> > At yesterday's dev meetup -- minutes to follow -- it was suggested we
>> move
>> > the project to git as our repo of truth.
>> >
>> > What do folks think? How patches are contributed and committer will have
>> > to change to match git-flow.
>> >
>> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
>> was
>> > kind enough to write up the steps involved moving their project over.
>> See
>> > the discussion on how they come up w/ a process in particular.
>> >
>> > St.Ack
>> >
>> >
>> >
>> > ---------- Forwarded message ----------
>> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
>> > Date: Fri, Oct 25, 2013 at 12:25 AM
>> > Subject: Accumulo's transition to git
>> > To: Stack <stack@duboce.net <javascript:;>>
>> >
>> >
>> > Stack,
>> >
>> > As promised, here's the info that I had collected when Accumulo made the
>> > transition from SVN to Git.
>> >
>> > Make sure you have some mailing list consensus, and then open up an INFRA
>> > ticket. For us, we requested the following things
>> >
>> > 1. Specify which SVN branches you want in Git, and if you want them
>> > renamed. Also, which you want the default Git branch to be on clone.
>> >
>> > 2. If you have any contribs, specify which other SVN path you want as
>> their
>> > own Git repos.
>> >
>> > 3. Specify the format of the subject for the git commit notifications
>> email
>> > and to which mailing list.
>> >
>> > 4. Request update of mirroring on git.a.o and github.com/apache/...
>> >
>> > 5. Transition from svn2jira to git2jira (honestly, I don't remember what
>> > this was anymore.. maybe commenting on Jira for issue mentions in
>> commits)
>> >
>> > 6. Request delivery of pull-requests to a given mailing list.
>> >
>> > 7. Request update reviewboard to the new repo.
>> >
>> > Our INFRA ticket can be found at [1]
>> >
>> > FWIW, we also had a huge discussion about how we were going to use Git so
>> > that we didn't constantly duplicate a bunch of commits cherry-picking
>> > changes everywhere. There was a bunch of teaching we had to do to make
>> sure
>> > we had a good commit history and could still use features like
>> git-bisect.
>> > The result of that is at [2].
>> >
>> > Joe Stein also sent us Kafka's use of Git that was helpful when writing
>> > down how users should contribute patches. [3]
>> >
>> > I hope all this helps! Despite the pain we went through in getting this
>> all
>> > set up (dealing with coordination of INFRA to lock the SVN repos,
>> transfer
>> > to Git, verify accuracy, and people who then didn't know how to use
>> Git), I
>> > think everyone is happy we did it.
>> >
>> > - Josh
>> >
>> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
>> > https://issues.apache.org/jira/browse/INFRA-6392>
>> > [2] http://accumulo.apache.org/**git.html<
>> > http://accumulo.apache.org/git.html>
>> > [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
>> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
>> > [4] https://git-wip-us.apache.org/
>> >
>>
>>
>> --
>> -------------------
>> Jesse Yates
>> @jesse_yates
>> jyates.github.com
>>
--
Best Regards,
Haosdent Huang
Re: DISCUSSION: Move to GIT?
Posted by Ted Yu <yu...@gmail.com>.
+1 too.
On Fri, Oct 25, 2013 at 10:07 AM, Jesse Yates <je...@gmail.com>wrote:
> +1
>
> Do all my work in git anyways :)
>
> On Friday, October 25, 2013, Stack wrote:
>
> > At yesterday's dev meetup -- minutes to follow -- it was suggested we
> move
> > the project to git as our repo of truth.
> >
> > What do folks think? How patches are contributed and committer will have
> > to change to match git-flow.
> >
> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
> was
> > kind enough to write up the steps involved moving their project over.
> See
> > the discussion on how they come up w/ a process in particular.
> >
> > St.Ack
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > Subject: Accumulo's transition to git
> > To: Stack <stack@duboce.net <javascript:;>>
> >
> >
> > Stack,
> >
> > As promised, here's the info that I had collected when Accumulo made the
> > transition from SVN to Git.
> >
> > Make sure you have some mailing list consensus, and then open up an INFRA
> > ticket. For us, we requested the following things
> >
> > 1. Specify which SVN branches you want in Git, and if you want them
> > renamed. Also, which you want the default Git branch to be on clone.
> >
> > 2. If you have any contribs, specify which other SVN path you want as
> their
> > own Git repos.
> >
> > 3. Specify the format of the subject for the git commit notifications
> email
> > and to which mailing list.
> >
> > 4. Request update of mirroring on git.a.o and github.com/apache/...
> >
> > 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> > this was anymore.. maybe commenting on Jira for issue mentions in
> commits)
> >
> > 6. Request delivery of pull-requests to a given mailing list.
> >
> > 7. Request update reviewboard to the new repo.
> >
> > Our INFRA ticket can be found at [1]
> >
> > FWIW, we also had a huge discussion about how we were going to use Git so
> > that we didn't constantly duplicate a bunch of commits cherry-picking
> > changes everywhere. There was a bunch of teaching we had to do to make
> sure
> > we had a good commit history and could still use features like
> git-bisect.
> > The result of that is at [2].
> >
> > Joe Stein also sent us Kafka's use of Git that was helpful when writing
> > down how users should contribute patches. [3]
> >
> > I hope all this helps! Despite the pain we went through in getting this
> all
> > set up (dealing with coordination of INFRA to lock the SVN repos,
> transfer
> > to Git, verify accuracy, and people who then didn't know how to use
> Git), I
> > think everyone is happy we did it.
> >
> > - Josh
> >
> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > https://issues.apache.org/jira/browse/INFRA-6392>
> > [2] http://accumulo.apache.org/**git.html<
> > http://accumulo.apache.org/git.html>
> > [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > [4] https://git-wip-us.apache.org/
> >
>
>
> --
> -------------------
> Jesse Yates
> @jesse_yates
> jyates.github.com
>
Re: DISCUSSION: Move to GIT?
Posted by Jesse Yates <je...@gmail.com>.
+1
Do all my work in git anyways :)
On Friday, October 25, 2013, Stack wrote:
> At yesterday's dev meetup -- minutes to follow -- it was suggested we move
> the project to git as our repo of truth.
>
> What do folks think? How patches are contributed and committer will have
> to change to match git-flow.
>
> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
> kind enough to write up the steps involved moving their project over. See
> the discussion on how they come up w/ a process in particular.
>
> St.Ack
>
>
>
> ---------- Forwarded message ----------
> From: Josh Elser <josh.elser@gmail.com <javascript:;>>
> Date: Fri, Oct 25, 2013 at 12:25 AM
> Subject: Accumulo's transition to git
> To: Stack <stack@duboce.net <javascript:;>>
>
>
> Stack,
>
> As promised, here's the info that I had collected when Accumulo made the
> transition from SVN to Git.
>
> Make sure you have some mailing list consensus, and then open up an INFRA
> ticket. For us, we requested the following things
>
> 1. Specify which SVN branches you want in Git, and if you want them
> renamed. Also, which you want the default Git branch to be on clone.
>
> 2. If you have any contribs, specify which other SVN path you want as their
> own Git repos.
>
> 3. Specify the format of the subject for the git commit notifications email
> and to which mailing list.
>
> 4. Request update of mirroring on git.a.o and github.com/apache/...
>
> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> this was anymore.. maybe commenting on Jira for issue mentions in commits)
>
> 6. Request delivery of pull-requests to a given mailing list.
>
> 7. Request update reviewboard to the new repo.
>
> Our INFRA ticket can be found at [1]
>
> FWIW, we also had a huge discussion about how we were going to use Git so
> that we didn't constantly duplicate a bunch of commits cherry-picking
> changes everywhere. There was a bunch of teaching we had to do to make sure
> we had a good commit history and could still use features like git-bisect.
> The result of that is at [2].
>
> Joe Stein also sent us Kafka's use of Git that was helpful when writing
> down how users should contribute patches. [3]
>
> I hope all this helps! Despite the pain we went through in getting this all
> set up (dealing with coordination of INFRA to lock the SVN repos, transfer
> to Git, verify accuracy, and people who then didn't know how to use Git), I
> think everyone is happy we did it.
>
> - Josh
>
> [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> https://issues.apache.org/jira/browse/INFRA-6392>
> [2] http://accumulo.apache.org/**git.html<
> http://accumulo.apache.org/git.html>
> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> [4] https://git-wip-us.apache.org/
>
--
-------------------
Jesse Yates
@jesse_yates
jyates.github.com
Re: DISCUSSION: Move to GIT?
Posted by ramkrishna vasudevan <ra...@gmail.com>.
+1 from me.
On Sun, Oct 27, 2013 at 9:50 AM, Stack <st...@duboce.net> wrote:
> On Sat, Oct 26, 2013 at 9:12 PM, Talat UYARER <talat.uyarer@agmlab.com
> >wrote:
>
> > Hi Stack,
> >
> > I am volunteer for conversion.
> >
>
> You are a gentleman Talat.
>
> My guess is that you may not be able to make much progress if you are not a
> committer but if you want to see how far you can get, I'd be game. Keep me
> in the loop and I can do any necessary committer intercessions.
>
> Yours,
> St.Ack
>
Re: DISCUSSION: Move to GIT?
Posted by Stack <st...@duboce.net>.
On Sat, Oct 26, 2013 at 9:12 PM, Talat UYARER <ta...@agmlab.com>wrote:
> Hi Stack,
>
> I am volunteer for conversion.
>
You are a gentleman Talat.
My guess is that you may not be able to make much progress if you are not a
committer but if you want to see how far you can get, I'd be game. Keep me
in the loop and I can do any necessary committer intercessions.
Yours,
St.Ack
Re: DISCUSSION: Move to GIT?
Posted by Talat UYARER <ta...@agmlab.com>.
Hi Stack,
I am volunteer for conversion.
Talat
27-10-2013 02:01 tarihinde, Stack yazdı:
> I'd say the vote carries.
>
> Any volunteers to run the conversion project?
>
> (If none, we'll get the caretaker to do it!)
>
> St.Ack
>
>
> On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
>
>> At yesterday's dev meetup -- minutes to follow -- it was suggested we move
>> the project to git as our repo of truth.
>>
>> What do folks think? How patches are contributed and committer will have
>> to change to match git-flow.
>>
>> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
>> kind enough to write up the steps involved moving their project over. See
>> the discussion on how they come up w/ a process in particular.
>>
>> St.Ack
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Josh Elser <jo...@gmail.com>
>> Date: Fri, Oct 25, 2013 at 12:25 AM
>> Subject: Accumulo's transition to git
>> To: Stack <st...@duboce.net>
>>
>>
>> Stack,
>>
>> As promised, here's the info that I had collected when Accumulo made the
>> transition from SVN to Git.
>>
>> Make sure you have some mailing list consensus, and then open up an INFRA
>> ticket. For us, we requested the following things
>>
>> 1. Specify which SVN branches you want in Git, and if you want them
>> renamed. Also, which you want the default Git branch to be on clone.
>>
>> 2. If you have any contribs, specify which other SVN path you want as
>> their own Git repos.
>>
>> 3. Specify the format of the subject for the git commit notifications
>> email and to which mailing list.
>>
>> 4. Request update of mirroring on git.a.o and github.com/apache/...
>>
>> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
>> this was anymore.. maybe commenting on Jira for issue mentions in commits)
>>
>> 6. Request delivery of pull-requests to a given mailing list.
>>
>> 7. Request update reviewboard to the new repo.
>>
>> Our INFRA ticket can be found at [1]
>>
>> FWIW, we also had a huge discussion about how we were going to use Git so
>> that we didn't constantly duplicate a bunch of commits cherry-picking
>> changes everywhere. There was a bunch of teaching we had to do to make sure
>> we had a good commit history and could still use features like git-bisect.
>> The result of that is at [2].
>>
>> Joe Stein also sent us Kafka's use of Git that was helpful when writing
>> down how users should contribute patches. [3]
>>
>> I hope all this helps! Despite the pain we went through in getting this
>> all set up (dealing with coordination of INFRA to lock the SVN repos,
>> transfer to Git, verify accuracy, and people who then didn't know how to
>> use Git), I think everyone is happy we did it.
>>
>> - Josh
>>
>> [1] https://issues.apache.org/**jira/browse/INFRA-6392<https://issues.apache.org/jira/browse/INFRA-6392>
>> [2] http://accumulo.apache.org/**git.html<http://accumulo.apache.org/git.html>
>> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
>> [4] https://git-wip-us.apache.org/
>>
>>
>
Re: DISCUSSION: Move to GIT?
Posted by Stack <st...@duboce.net>.
I'd say the vote carries.
Any volunteers to run the conversion project?
(If none, we'll get the caretaker to do it!)
St.Ack
On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
> At yesterday's dev meetup -- minutes to follow -- it was suggested we move
> the project to git as our repo of truth.
>
> What do folks think? How patches are contributed and committer will have
> to change to match git-flow.
>
> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
> kind enough to write up the steps involved moving their project over. See
> the discussion on how they come up w/ a process in particular.
>
> St.Ack
>
>
>
> ---------- Forwarded message ----------
> From: Josh Elser <jo...@gmail.com>
> Date: Fri, Oct 25, 2013 at 12:25 AM
> Subject: Accumulo's transition to git
> To: Stack <st...@duboce.net>
>
>
> Stack,
>
> As promised, here's the info that I had collected when Accumulo made the
> transition from SVN to Git.
>
> Make sure you have some mailing list consensus, and then open up an INFRA
> ticket. For us, we requested the following things
>
> 1. Specify which SVN branches you want in Git, and if you want them
> renamed. Also, which you want the default Git branch to be on clone.
>
> 2. If you have any contribs, specify which other SVN path you want as
> their own Git repos.
>
> 3. Specify the format of the subject for the git commit notifications
> email and to which mailing list.
>
> 4. Request update of mirroring on git.a.o and github.com/apache/...
>
> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> this was anymore.. maybe commenting on Jira for issue mentions in commits)
>
> 6. Request delivery of pull-requests to a given mailing list.
>
> 7. Request update reviewboard to the new repo.
>
> Our INFRA ticket can be found at [1]
>
> FWIW, we also had a huge discussion about how we were going to use Git so
> that we didn't constantly duplicate a bunch of commits cherry-picking
> changes everywhere. There was a bunch of teaching we had to do to make sure
> we had a good commit history and could still use features like git-bisect.
> The result of that is at [2].
>
> Joe Stein also sent us Kafka's use of Git that was helpful when writing
> down how users should contribute patches. [3]
>
> I hope all this helps! Despite the pain we went through in getting this
> all set up (dealing with coordination of INFRA to lock the SVN repos,
> transfer to Git, verify accuracy, and people who then didn't know how to
> use Git), I think everyone is happy we did it.
>
> - Josh
>
> [1] https://issues.apache.org/**jira/browse/INFRA-6392<https://issues.apache.org/jira/browse/INFRA-6392>
> [2] http://accumulo.apache.org/**git.html<http://accumulo.apache.org/git.html>
> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> [4] https://git-wip-us.apache.org/
>
>
Re: DISCUSSION: Move to GIT?
Posted by Talat UYARER <ta...@agmlab.com>.
+1
Local development very easy With git. And I can try some patches just
creating local branch.
26-10-2013 11:24 tarihinde, Lars George yazdı:
> +1, same for me
> On Oct 26, 2013 2:26 AM, "Andrew Purtell" <ap...@apache.org> wrote:
>
>> +1
>>
>> I only use SVN when committing.
>>
>>
>> On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
>>
>>> At yesterday's dev meetup -- minutes to follow -- it was suggested we
>> move
>>> the project to git as our repo of truth.
>>>
>>> What do folks think? How patches are contributed and committer will have
>>> to change to match git-flow.
>>>
>>> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
>> was
>>> kind enough to write up the steps involved moving their project over.
>> See
>>> the discussion on how they come up w/ a process in particular.
>>>
>>> St.Ack
>>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Josh Elser <jo...@gmail.com>
>>> Date: Fri, Oct 25, 2013 at 12:25 AM
>>> Subject: Accumulo's transition to git
>>> To: Stack <st...@duboce.net>
>>>
>>>
>>> Stack,
>>>
>>> As promised, here's the info that I had collected when Accumulo made the
>>> transition from SVN to Git.
>>>
>>> Make sure you have some mailing list consensus, and then open up an INFRA
>>> ticket. For us, we requested the following things
>>>
>>> 1. Specify which SVN branches you want in Git, and if you want them
>>> renamed. Also, which you want the default Git branch to be on clone.
>>>
>>> 2. If you have any contribs, specify which other SVN path you want as
>> their
>>> own Git repos.
>>>
>>> 3. Specify the format of the subject for the git commit notifications
>> email
>>> and to which mailing list.
>>>
>>> 4. Request update of mirroring on git.a.o and github.com/apache/...
>>>
>>> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
>>> this was anymore.. maybe commenting on Jira for issue mentions in
>> commits)
>>>
>>> 6. Request delivery of pull-requests to a given mailing list.
>>>
>>> 7. Request update reviewboard to the new repo.
>>>
>>> Our INFRA ticket can be found at [1]
>>>
>>> FWIW, we also had a huge discussion about how we were going to use Git so
>>> that we didn't constantly duplicate a bunch of commits cherry-picking
>>> changes everywhere. There was a bunch of teaching we had to do to make
>> sure
>>> we had a good commit history and could still use features like
>> git-bisect.
>>> The result of that is at [2].
>>>
>>> Joe Stein also sent us Kafka's use of Git that was helpful when writing
>>> down how users should contribute patches. [3]
>>>
>>> I hope all this helps! Despite the pain we went through in getting this
>> all
>>> set up (dealing with coordination of INFRA to lock the SVN repos,
>> transfer
>>> to Git, verify accuracy, and people who then didn't know how to use
>> Git), I
>>> think everyone is happy we did it.
>>>
>>> - Josh
>>>
>>> [1] https://issues.apache.org/**jira/browse/INFRA-6392<
>>> https://issues.apache.org/jira/browse/INFRA-6392>
>>> [2] http://accumulo.apache.org/**git.html<
>>> http://accumulo.apache.org/git.html>
>>> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
>>> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
>>> [4] https://git-wip-us.apache.org/
>>>
>>
>>
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>
Re: DISCUSSION: Move to GIT?
Posted by Lars George <la...@gmail.com>.
+1, same for me
On Oct 26, 2013 2:26 AM, "Andrew Purtell" <ap...@apache.org> wrote:
> +1
>
> I only use SVN when committing.
>
>
> On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
>
> > At yesterday's dev meetup -- minutes to follow -- it was suggested we
> move
> > the project to git as our repo of truth.
> >
> > What do folks think? How patches are contributed and committer will have
> > to change to match git-flow.
> >
> > Josh Eiser, an accumulo committer, was at the dev meetup yesterday and
> was
> > kind enough to write up the steps involved moving their project over.
> See
> > the discussion on how they come up w/ a process in particular.
> >
> > St.Ack
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Josh Elser <jo...@gmail.com>
> > Date: Fri, Oct 25, 2013 at 12:25 AM
> > Subject: Accumulo's transition to git
> > To: Stack <st...@duboce.net>
> >
> >
> > Stack,
> >
> > As promised, here's the info that I had collected when Accumulo made the
> > transition from SVN to Git.
> >
> > Make sure you have some mailing list consensus, and then open up an INFRA
> > ticket. For us, we requested the following things
> >
> > 1. Specify which SVN branches you want in Git, and if you want them
> > renamed. Also, which you want the default Git branch to be on clone.
> >
> > 2. If you have any contribs, specify which other SVN path you want as
> their
> > own Git repos.
> >
> > 3. Specify the format of the subject for the git commit notifications
> email
> > and to which mailing list.
> >
> > 4. Request update of mirroring on git.a.o and github.com/apache/...
> >
> > 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> > this was anymore.. maybe commenting on Jira for issue mentions in
> commits)
> >
> > 6. Request delivery of pull-requests to a given mailing list.
> >
> > 7. Request update reviewboard to the new repo.
> >
> > Our INFRA ticket can be found at [1]
> >
> > FWIW, we also had a huge discussion about how we were going to use Git so
> > that we didn't constantly duplicate a bunch of commits cherry-picking
> > changes everywhere. There was a bunch of teaching we had to do to make
> sure
> > we had a good commit history and could still use features like
> git-bisect.
> > The result of that is at [2].
> >
> > Joe Stein also sent us Kafka's use of Git that was helpful when writing
> > down how users should contribute patches. [3]
> >
> > I hope all this helps! Despite the pain we went through in getting this
> all
> > set up (dealing with coordination of INFRA to lock the SVN repos,
> transfer
> > to Git, verify accuracy, and people who then didn't know how to use
> Git), I
> > think everyone is happy we did it.
> >
> > - Josh
> >
> > [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> > https://issues.apache.org/jira/browse/INFRA-6392>
> > [2] http://accumulo.apache.org/**git.html<
> > http://accumulo.apache.org/git.html>
> > [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> > https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> > [4] https://git-wip-us.apache.org/
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Re: DISCUSSION: Move to GIT?
Posted by Andrew Purtell <ap...@apache.org>.
+1
I only use SVN when committing.
On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
> At yesterday's dev meetup -- minutes to follow -- it was suggested we move
> the project to git as our repo of truth.
>
> What do folks think? How patches are contributed and committer will have
> to change to match git-flow.
>
> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
> kind enough to write up the steps involved moving their project over. See
> the discussion on how they come up w/ a process in particular.
>
> St.Ack
>
>
>
> ---------- Forwarded message ----------
> From: Josh Elser <jo...@gmail.com>
> Date: Fri, Oct 25, 2013 at 12:25 AM
> Subject: Accumulo's transition to git
> To: Stack <st...@duboce.net>
>
>
> Stack,
>
> As promised, here's the info that I had collected when Accumulo made the
> transition from SVN to Git.
>
> Make sure you have some mailing list consensus, and then open up an INFRA
> ticket. For us, we requested the following things
>
> 1. Specify which SVN branches you want in Git, and if you want them
> renamed. Also, which you want the default Git branch to be on clone.
>
> 2. If you have any contribs, specify which other SVN path you want as their
> own Git repos.
>
> 3. Specify the format of the subject for the git commit notifications email
> and to which mailing list.
>
> 4. Request update of mirroring on git.a.o and github.com/apache/...
>
> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> this was anymore.. maybe commenting on Jira for issue mentions in commits)
>
> 6. Request delivery of pull-requests to a given mailing list.
>
> 7. Request update reviewboard to the new repo.
>
> Our INFRA ticket can be found at [1]
>
> FWIW, we also had a huge discussion about how we were going to use Git so
> that we didn't constantly duplicate a bunch of commits cherry-picking
> changes everywhere. There was a bunch of teaching we had to do to make sure
> we had a good commit history and could still use features like git-bisect.
> The result of that is at [2].
>
> Joe Stein also sent us Kafka's use of Git that was helpful when writing
> down how users should contribute patches. [3]
>
> I hope all this helps! Despite the pain we went through in getting this all
> set up (dealing with coordination of INFRA to lock the SVN repos, transfer
> to Git, verify accuracy, and people who then didn't know how to use Git), I
> think everyone is happy we did it.
>
> - Josh
>
> [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> https://issues.apache.org/jira/browse/INFRA-6392>
> [2] http://accumulo.apache.org/**git.html<
> http://accumulo.apache.org/git.html>
> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> [4] https://git-wip-us.apache.org/
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: DISCUSSION: Move to GIT?
Posted by Dave Wang <ds...@cloudera.com>.
(non-binding) +1
On Fri, Oct 25, 2013 at 9:45 AM, Stack <st...@duboce.net> wrote:
> At yesterday's dev meetup -- minutes to follow -- it was suggested we move
> the project to git as our repo of truth.
>
> What do folks think? How patches are contributed and committer will have
> to change to match git-flow.
>
> Josh Eiser, an accumulo committer, was at the dev meetup yesterday and was
> kind enough to write up the steps involved moving their project over. See
> the discussion on how they come up w/ a process in particular.
>
> St.Ack
>
>
>
> ---------- Forwarded message ----------
> From: Josh Elser <jo...@gmail.com>
> Date: Fri, Oct 25, 2013 at 12:25 AM
> Subject: Accumulo's transition to git
> To: Stack <st...@duboce.net>
>
>
> Stack,
>
> As promised, here's the info that I had collected when Accumulo made the
> transition from SVN to Git.
>
> Make sure you have some mailing list consensus, and then open up an INFRA
> ticket. For us, we requested the following things
>
> 1. Specify which SVN branches you want in Git, and if you want them
> renamed. Also, which you want the default Git branch to be on clone.
>
> 2. If you have any contribs, specify which other SVN path you want as their
> own Git repos.
>
> 3. Specify the format of the subject for the git commit notifications email
> and to which mailing list.
>
> 4. Request update of mirroring on git.a.o and github.com/apache/...
>
> 5. Transition from svn2jira to git2jira (honestly, I don't remember what
> this was anymore.. maybe commenting on Jira for issue mentions in commits)
>
> 6. Request delivery of pull-requests to a given mailing list.
>
> 7. Request update reviewboard to the new repo.
>
> Our INFRA ticket can be found at [1]
>
> FWIW, we also had a huge discussion about how we were going to use Git so
> that we didn't constantly duplicate a bunch of commits cherry-picking
> changes everywhere. There was a bunch of teaching we had to do to make sure
> we had a good commit history and could still use features like git-bisect.
> The result of that is at [2].
>
> Joe Stein also sent us Kafka's use of Git that was helpful when writing
> down how users should contribute patches. [3]
>
> I hope all this helps! Despite the pain we went through in getting this all
> set up (dealing with coordination of INFRA to lock the SVN repos, transfer
> to Git, verify accuracy, and people who then didn't know how to use Git), I
> think everyone is happy we did it.
>
> - Josh
>
> [1] https://issues.apache.org/**jira/browse/INFRA-6392<
> https://issues.apache.org/jira/browse/INFRA-6392>
> [2] http://accumulo.apache.org/**git.html<
> http://accumulo.apache.org/git.html>
> [3] https://cwiki.apache.org/**confluence/display/KAFKA/Git+**Workflow<
> https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow>
> [4] https://git-wip-us.apache.org/
>