hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colin McCabe <cmcc...@alumni.cmu.edu>
Subject Re: Updates on migration to git
Date Wed, 27 Aug 2014 20:42:58 GMT
Thanks for making this happen, Karthik and Daniel.  Great job.

best,
Colin

On Tue, Aug 26, 2014 at 5:59 PM, Karthik Kambatla <kasha@cloudera.com> wrote:
> Yes, we have requested for force-push disabled on trunk and branch-*
> branches. I didn't test it though :P, it is not writable yet.
>
>
> On Tue, Aug 26, 2014 at 5:48 PM, Todd Lipcon <todd@cloudera.com> wrote:
>
>> Hey Karthik,
>>
>> Just to confirm, have we disabled force-push support on the repo?
>>
>> In my experience, especially when a project has committers new to git,
>> force-push support causes more trouble than it's worth.
>>
>> -Todd
>>
>>
>> On Tue, Aug 26, 2014 at 4:39 PM, Karthik Kambatla <kasha@cloudera.com>
>> wrote:
>>
>> > Looks like our git repo is good to go.
>> >
>> > On INFRA-8195, I am asking Daniel to enable writing to it. In case you
>> find
>> > any issues, please comment on the JIRA.
>> >
>> > Thanks
>> > Karthik
>> >
>> >
>> > On Tue, Aug 26, 2014 at 3:28 PM, Arpit Agarwal <aagarwal@hortonworks.com
>> >
>> > wrote:
>> >
>> > > I cloned the new repo, built trunk and branch-2, verified all the
>> > branches
>> > > are present. Also checked a few branches and the recent commit history
>> > > matches our existing repo. Everything looks good so far.
>> > >
>> > >
>> > > On Tue, Aug 26, 2014 at 1:19 PM, Karthik Kambatla <kasha@cloudera.com>
>> > > wrote:
>> > >
>> > > > The git repository is now ready for inspection. I ll take a look
>> > shortly,
>> > > > but it would be great if a few others could too.
>> > > >
>> > > > Once we are okay with it, we can ask it to be writable.
>> > > >
>> > > > On Tuesday, August 26, 2014, Karthik Kambatla <kasha@cloudera.com>
>> > > wrote:
>> > > >
>> > > > > Hi Suresh
>> > > > >
>> > > > > There was one vote thread on whether to migrate to git, and the
>> > > > > implications to the commit process for individual patches and
>> feature
>> > > > > branches -
>> > > > >
>> > >
>> https://www.mail-archive.com/common-dev@hadoop.apache.org/msg13447.html
>> > > > .
>> > > > > Prior to that, there was a discuss thread on the same topic.
>> > > > >
>> > > > > As INFRA handles the actual migration from subversion to git,
the
>> > vote
>> > > > > didn't include those specifics. The migration is going on as
we
>> speak
>> > > > (See
>> > > > > INFRA-8195). The initial expectation was that the migration would
>> be
>> > > done
>> > > > > in a few hours, but it has been several hours and the last I
heard
>> > the
>> > > > > import was still running.
>> > > > >
>> > > > > I have elaborated on the points in the vote thread and drafted
up a
>> > > wiki
>> > > > > page on how-to-commit -
>> > > > https://wiki.apache.org/hadoop/HowToCommitWithGit
>> > > > > . We can work on improving this further and call a vote thread
on
>> > those
>> > > > > items if need be.
>> > > > >
>> > > > > Thanks
>> > > > > Karthik
>> > > > >
>> > > > >
>> > > > > On Tue, Aug 26, 2014 at 11:41 AM, Suresh Srinivas <
>> > > > suresh@hortonworks.com
>> > > > > <javascript:_e(%7B%7D,'cvml','suresh@hortonworks.com');>>
wrote:
>> > > > >
>> > > > >> Karthik,
>> > > > >>
>> > > > >> I would like to see detailed information on how this migration
>> will
>> > be
>> > > > >> done, how it will affect the existing project and commit
process.
>> > This
>> > > > >> should be done in a document that can be reviewed instead
of in an
>> > > email
>> > > > >> thread on an ad-hoc basis. Was there any voting on this in
PMC and
>> > > > should
>> > > > >> we have a vote to ensure everyone is one the same page on
doing
>> this
>> > > and
>> > > > >> how to go about it?
>> > > > >>
>> > > > >> Regards,
>> > > > >> Suresh
>> > > > >>
>> > > > >>
>> > > > >> On Tue, Aug 26, 2014 at 9:17 AM, Karthik Kambatla <
>> > kasha@cloudera.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','kasha@cloudera.com');>>
>> > > > >> wrote:
>> > > > >>
>> > > > >> > Last I heard, the import is still going on and appears
closer to
>> > > > getting
>> > > > >> > done. Thanks for your patience with the migration.
>> > > > >> >
>> > > > >> > I ll update you as and when there is something. Eventually,
the
>> > git
>> > > > repo
>> > > > >> > should be at the location in the wiki.
>> > > > >> >
>> > > > >> >
>> > > > >> > On Mon, Aug 25, 2014 at 3:45 PM, Karthik Kambatla <
>> > > kasha@cloudera.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','kasha@cloudera.com');>>
>> > > > >> > wrote:
>> > > > >> >
>> > > > >> > > Thanks for bringing these points up, Zhijie.
>> > > > >> > >
>> > > > >> > > By the way, a revised How-to-commit wiki is at:
>> > > > >> > > https://wiki.apache.org/hadoop/HowToCommitWithGit
. Please
>> feel
>> > > > free
>> > > > >> to
>> > > > >> > > make changes and improve it.
>> > > > >> > >
>> > > > >> > > On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen <
>> > > > zshen@hortonworks.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','zshen@hortonworks.com');>>
>> > > > >> > > wrote:
>> > > > >> > >
>> > > > >> > >> Do we have any convention about "user.name"
and
>> "user.email"?
>> > > For
>> > > > >> > >> example,
>> > > > >> > >> we'd like to use @apache.org for the email.
>> > > > >> > >>
>> > > > >> > >
>> > > > >> > > May be, we can ask people to use project-specific
configs here
>> > and
>> > > > use
>> > > > >> > > their real name and @apache.org address.
>> > > > >> > >
>> > > > >> > > Is there any downside to letting people use their
global
>> values
>> > > for
>> > > > >> these
>> > > > >> > > configs?
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >>
>> > > > >> > >> Moreover, do we want to use "--author="Author
Name <
>> > > > >> email@address.com <javascript:_e(%7B%7D,'cvml','email@address.com
>> > > ');>>"
>> > > > >> > >> when committing on behalf of a particular contributor?
>> > > > >> > >>
>> > > > >> > >
>> > > > >> > > Fetching the email-address is complicated here.
Should we use
>> > the
>> > > > >> > > contributor's email from JIRA? What if that is
not their
>> @apache
>> > > > >> address?
>> > > > >> > >
>> > > > >> > >
>> > > > >> > >>
>> > > > >> > >>
>> > > > >> > >> On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla
<
>> > > > >> kasha@cloudera.com <javascript:_e(%7B%7D,'cvml','
>> kasha@cloudera.com
>> > > > ');>>
>> > > > >> > >> wrote:
>> > > > >> > >>
>> > > > >> > >> > Thanks for your input, Steve. Sorry for
sending the email
>> out
>> > > > that
>> > > > >> > >> late, I
>> > > > >> > >> > sent it as soon as I could.
>> > > > >> > >> >
>> > > > >> > >> >
>> > > > >> > >> > On Mon, Aug 25, 2014 at 2:20 AM, Steve
Loughran <
>> > > > >> > stevel@hortonworks.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','stevel@hortonworks.com');>
>> > > > >> > >> >
>> > > > >> > >> > wrote:
>> > > > >> > >> >
>> > > > >> > >> > > just caught up with this after some
offlininess...15:48
>> PST
>> > > is
>> > > > >> too
>> > > > >> > >> late
>> > > > >> > >> > for
>> > > > >> > >> > > me.
>> > > > >> > >> > >
>> > > > >> > >> > > I'd be -1 to a change to "master"
because of that risk
>> that
>> > > it
>> > > > >> does
>> > > > >> > >> break
>> > > > >> > >> > > existing code -especially people
that have trunk off the
>> > git
>> > > > >> mirrors
>> > > > >> > >> and
>> > > > >> > >> > > automated builds/merges to go with
it.
>> > > > >> > >> > >
>> > > > >> > >> >
>> > > > >> > >> > Fair enough. It makes sense to leave it
as "trunk", unless
>> > > > someone
>> > > > >> is
>> > > > >> > >> > against it being trunk.
>> > > > >> > >> >
>> > > > >> > >> >
>> > > > >> > >> > >
>> > > > >> > >> > > "master" may be viewed as the official
git way, but it
>> > > doesn't
>> > > > >> have
>> > > > >> > to
>> > > > >> > >> > be.
>> > > > >> > >> > > For git-flow workflows (which we
use in slider) master/
>> is
>> > > for
>> > > > >> > >> releases,
>> > > > >> > >> > > develop/ for dev.
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > >
>> > > > >> > >> > > On 24 August 2014 02:31, Karthik
Kambatla <
>> > > kasha@cloudera.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','kasha@cloudera.com');>>
>> > > > >> > wrote:
>> > > > >> > >> > >
>> > > > >> > >> > > > Couple of things:
>> > > > >> > >> > > >
>> > > > >> > >> > > > 1. Since no one expressed any
reservations against
>> doing
>> > > this
>> > > > >> on
>> > > > >> > >> Sunday
>> > > > >> > >> > > or
>> > > > >> > >> > > > renaming trunk to master, I
ll go ahead and confirm
>> > that. I
>> > > > >> think
>> > > > >> > >> that
>> > > > >> > >> > > > serves us better in the long
run.
>> > > > >> > >> > > >
>> > > > >> > >> > > > 2. Arpit brought up the precommit
builds - we should
>> > > > definitely
>> > > > >> > fix
>> > > > >> > >> > them
>> > > > >> > >> > > as
>> > > > >> > >> > > > soon as we can. I understand
Giri maintains those
>> builds,
>> > > do
>> > > > we
>> > > > >> > have
>> > > > >> > >> > > anyone
>> > > > >> > >> > > > else who has access in case
Giri is not reachable?
>> Giri -
>> > > > >> please
>> > > > >> > >> shout
>> > > > >> > >> > > out
>> > > > >> > >> > > > if you can help us with this
either on Sunday or
>> Monday.
>> > > > >> > >> > > >
>> > > > >> > >> > > > Thanks
>> > > > >> > >> > > > Karthik
>> > > > >> > >> > > >
>> > > > >> > >> > > >
>> > > > >> > >> > > >
>> > > > >> > >> > > >
>> > > > >> > >> > > > On Fri, Aug 22, 2014 at 3:50
PM, Karthik Kambatla <
>> > > > >> > >> kasha@cloudera.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','kasha@cloudera.com');>>
>> > > > >> > >> > > > wrote:
>> > > > >> > >> > > >
>> > > > >> > >> > > > > Also, does anyone know
what we use for integration
>> > > between
>> > > > >> JIRA
>> > > > >> > >> and
>> > > > >> > >> > > svn?
>> > > > >> > >> > > > I
>> > > > >> > >> > > > > am assuming svn2jira.
>> > > > >> > >> > > > >
>> > > > >> > >> > > > >
>> > > > >> > >> > > > > On Fri, Aug 22, 2014 at
3:48 PM, Karthik Kambatla <
>> > > > >> > >> > kasha@cloudera.com
>> > > > >> <javascript:_e(%7B%7D,'cvml','kasha@cloudera.com');>>
>> > > > >> > >> > > > > wrote:
>> > > > >> > >> > > > >
>> > > > >> > >> > > > >> Hi folks,
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >> For the SCM migration,
feel free to follow
>> > > > >> > >> > > > >> https://issues.apache.org/jira/browse/INFRA-8195
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >> Most of this is planned
to be handled this Sunday.
>> As
>> > a
>> > > > >> result,
>> > > > >> > >> the
>> > > > >> > >> > > > >> subversion repository
would be read-only. If this
>> is a
>> > > > major
>> > > > >> > >> issue
>> > > > >> > >> > for
>> > > > >> > >> > > > you,
>> > > > >> > >> > > > >> please shout out.
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >> Daniel Gruno, the one
helping us with the migration,
>> > was
>> > > > >> asking
>> > > > >> > >> if
>> > > > >> > >> > we
>> > > > >> > >> > > > are
>> > > > >> > >> > > > >> open to renaming "trunk"
to "master" to better
>> conform
>> > > to
>> > > > >> git
>> > > > >> > >> > lingo. I
>> > > > >> > >> > > > am
>> > > > >> > >> > > > >> tempted to say yes,
but wanted to check.
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >> Would greatly appreciate
any help with checking the
>> > git
>> > > > repo
>> > > > >> > has
>> > > > >> > >> > > > >> everything.
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >> Thanks
>> > > > >> > >> > > > >> Karthik
>> > > > >> > >> > > > >>
>> > > > >> > >> > > > >
>> > > > >> > >> > > > >
>> > > > >> > >> > > >
>> > > > >> > >> > >
>> > > > >> > >> > > --
>> > > > >> > >> > > 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.
>> > > > >> > >> > >
>> > > > >> > >> >
>> > > > >> > >>
>> > > > >> > >>
>> > > > >> > >>
>> > > > >> > >> --
>> > > > >> > >> Zhijie Shen
>> > > > >> > >> Hortonworks Inc.
>> > > > >> > >> http://hortonworks.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.
>> > > > >> > >>
>> > > > >> > >
>> > > > >> > >
>> > > > >> >
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >> --
>> > > > >> http://hortonworks.com/download/
>> > > > >>
>> > > > >> --
>> > > > >> 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.
>> > > > >>
>> > > > >
>> > > > >
>> > > >
>> > > > --
>> > > > Mobile
>> > > >
>> > >
>> > > --
>> > > 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.
>> > >
>> >
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>

Mime
View raw message