hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karthik Kambatla <ka...@cloudera.com>
Subject Re: Updates on migration to git
Date Tue, 26 Aug 2014 16:17:17 GMT
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>
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>
> 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>"
>> 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>
>> 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
>> >
>> > 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> 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>
>> > > > 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>
>> > > > > 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.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message