Thanks Giri. By the way, writes to svn are now disabled.
On Saturday, August 23, 2014, Giridharan Kesavan <gkesa...@hortonworks.com> wrote: > I can take a look at this on Monday. > > -giri > > > On Sat, Aug 23, 2014 at 6:31 PM, Karthik Kambatla <ka...@cloudera.com > <javascript:;>> > 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 <ka...@cloudera.com > <javascript:;>> > > 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 <ka...@cloudera.com > <javascript:;>> > > > 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. > -- Mobile
