Return-Path: X-Original-To: apmail-pig-dev-archive@www.apache.org Delivered-To: apmail-pig-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB415E5AF for ; Tue, 5 Feb 2013 16:19:02 +0000 (UTC) Received: (qmail 89329 invoked by uid 500); 5 Feb 2013 16:19:02 -0000 Delivered-To: apmail-pig-dev-archive@pig.apache.org Received: (qmail 87930 invoked by uid 500); 5 Feb 2013 16:18:56 -0000 Mailing-List: contact dev-help@pig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pig.apache.org Delivered-To: mailing list dev@pig.apache.org Received: (qmail 87885 invoked by uid 99); 5 Feb 2013 16:18:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 16:18:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [194.228.2.91] (HELO smtp-out3.iol.cz) (194.228.2.91) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 16:18:48 +0000 Received: from antivir5.iol.cz (unknown [192.168.30.212]) by smtp-out3.iol.cz (Postfix) with ESMTP id 5976E389A1 for ; Tue, 5 Feb 2013 17:18:26 +0100 (CET) Received: from localhost (antivir5.iol.cz [127.0.0.1]) by antivir5.iol.cz (Postfix) with ESMTP id 422C11E803A for ; Tue, 5 Feb 2013 17:18:26 +0100 (CET) X-Virus-Scanned: amavisd-new at iol.cz Received: from antivir5.iol.cz ([127.0.0.1]) by localhost (antivir5.iol.cz [127.0.0.1]) (amavisd-new, port 10224) with LMTP id CnsA0nIWhVTt for ; Tue, 5 Feb 2013 17:18:26 +0100 (CET) Received: from port4.iol.cz (unknown [192.168.30.94]) by antivir5.iol.cz (Postfix) with ESMTP id 06E271E804A for ; Tue, 5 Feb 2013 17:18:26 +0100 (CET) X-SBRS: None X-SBRS-none: None X-RECVLIST: MTA-OUT-IOL X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArI4AMovEVFBMsSC/2dsb2JhbABFhziyE4Ysc4IfAQEFbhsIAxgJJQ8FDU8Uh2sDDwyqN4ZLDYlWjBZ9EIQ4A4hmi2OBV4EeiD0EgWGFE4MfgU4 X-IPAS-Result: ArI4AMovEVFBMsSC/2dsb2JhbABFhziyE4Ysc4IfAQEFbhsIAxgJJQ8FDU8Uh2sDDwyqN4ZLDYlWjBZ9EIQ4A4hmi2OBV4EeiD0EgWGFE4MfgU4 Received: from connect-mtv.cloudera.com (HELO jarcec-thinkpad) ([65.50.196.130]) by port4.iol.cz with ESMTP; 05 Feb 2013 17:18:25 +0100 Date: Tue, 5 Feb 2013 08:18:20 -0800 From: Jarek Jarcec Cecho To: dev@pig.apache.org Subject: Re: Move pig project from svn to git repository Message-ID: <20130205161820.GH14835@jarcec-thinkpad> References: <20130202024620.GA12232@jarcec-thinkpad> <20130203215403.GC3756@localhost> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U3BNvdZEnlJXqmh+" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Checked: Checked by ClamAV on apache.org --U3BNvdZEnlJXqmh+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Guys, thank you for the feedback and linking previous discussion. I should have s= earch mailing list history prior sending my question. All the projects that I participate in and that moved to git still uses the= same patch-file-based contribution process as it was in place when there w= ere on SVN. We had short discussion [1] about using Gerrit [2] for code rev= iews rather than Review board which would make contribution process little = bit more straightforward but the discussion has died without real outcome. Jarcec Links: 1: http://markmail.org/message/262picjrvzep2k6a 2: http://code.google.com/p/gerrit/ On Mon, Feb 04, 2013 at 12:42:50PM -0800, Julien Le Dem wrote: > Sure, I'm more interested in how our patch-file-based contribution process > would be improved by moving to git. > I'm not against it but I'd like we think this through. > So my question is: > How would someone contribute once we move to git? How do they attach their > work to a jira? (patch file, pointer to a branch?) > Only committers would be able to create branches in the apache git repo, > would we save the contribution in a branch for that jira or do we still a= sk > for file patches ? >=20 >=20 > On Mon, Feb 4, 2013 at 11:13 AM, Russell Jurney wrote: >=20 > > Others (Cassandra?) have trail blazed already. > > > > > > On Mon, Feb 4, 2013 at 10:44 AM, Julien Le Dem wro= te: > > > > > There was a thread about this last year: > > > http://mail-archives.apache.org/mod_mbox/pig-dev/201203.mbox/thread?5 > > > As I recall there was no opposition but also no strong motivation to = be > > > trailblazers in this area. > > > I do see lag on the git mirror sometimes (hours). > > > I'd like to see a better process than the file based patch contributi= on > > but > > > it is unclear using git primarily will allow that. If you have > > suggestions > > > I'd be happy to hear about it. > > > Julien > > > > > > > > > On Sun, Feb 3, 2013 at 1:54 PM, Jarek Jarcec Cecho > > >wrote: > > > > > > > Hi Bill, > > > > thank you very much for your feedback. Mostly in the past the > > > > synchronization did not seemed reliable and sometimes it took coupl= e of > > > > hours or days to get latest updates from from svn to the git mirror. > > Also > > > > even recently, sometimes the mirrors seems unresponsive. At least f= or > > me. > > > > I'm not experiencing such issues when I'm working with the projects > > that > > > > are primarily running on git. Thus I was wondering whether pig > > community > > > > would be open to such migration. > > > > > > > > Jarcec > > > > > > > > On Fri, Feb 01, 2013 at 10:38:00PM -0800, Bill Graham wrote: > > > > > I'm a huge fan of git and use it exclusively for Pig with the > > exception > > > > of > > > > > committing patches. I haven't personally experienced any reliabil= ity > > > > issues > > > > > with the git mirror. What are the reliability issues you've seen? > > > > > > > > > > > > > > > On Fri, Feb 1, 2013 at 6:46 PM, Jarek Jarcec Cecho < > > jarcec@apache.org > > > > >wrote: > > > > > > > > > > > Hi pig developers, > > > > > > I personally prefer git over svn, so I'm using the git mirrors = that > > > > Apache > > > > > > provides. As those mirrors do not seem entirely reliable I was > > > > wondering > > > > > > whether there are other pig developers that also prefer git over > > svn > > > as > > > > > > myself. Apache Infrastructure Team is supporting projects that = are > > > > > > primarily working with git, so my question is - would pig devel= oper > > > > > > community be interested in migrating the repository from svn to > > git? > > > > > > > > > > > > I've recently participated in three projects that done this cha= nge, > > > > namely > > > > > > Sqoop, Flume and MRunit, and it's not a big deal. The process is > > > rather > > > > > > simple, just it take some time as most of the job is done by > > > > Infrastructure > > > > > > team. I would be more than happy to help or even drive the proc= ess > > in > > > > case > > > > > > that this change would be desirable by community. > > > > > > > > > > > > Jarcec > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > *Note that I'm no longer using my Yahoo! email address. Please em= ail > > me > > > > at > > > > > billgraham@gmail.com going forward.* > > > > > > > > > > > > > > > -- > > Russell Jurney twitter.com/rjurney russell.jurney@gmail.com > > datasyndrome.com > > --U3BNvdZEnlJXqmh+ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJRETDMAAoJEEk45sAabwqG1jsP/Rl6Qn5ws4QpHn6XRt6/d9Js PGRBuLQAXlUA3D9DpE6z7zDvbIxrKFm9EE3DchxDWcFyZRfU6W1YMOTYFfDSaG1E XbD8veH43D4NexcHqEy1jTiOrK/pAyMAx6uiyuIBAv+uMVgCvYrHkYmTrnxNz1PA NdWTmg230FFNZ17dU52mhVaw6O2tdY2kl/cNFjSE/k3bvgLxobhdeU+lu+GRd1ji hZe4nyPbrNfVAfVka114+y7pOxuKx48xCj9/lb48YKmitkVoxNJsFcIJIn1c977n mrFwnD26nwX5Cr52Ok3QUzaMF+wP06urKrC58fy4UDKnNZuURri70QFTQcOZOlOA ztI2lQiBovvjMM7Zt6H3crbRQbLgtzDnzNVj/5FalV+XwPQcqMkzimT6cctUJSlk aghTlax5jWq/dzko8h8sDMbiy2fH0oq45E9nFPRTUCnuBtOe1G1M1iqpYiAYAqyG QSxjmttfM2FWMl/X9DeO9hq2EQT9N/FoolbsUkTnIGAW85OFjOTu+K8axk7fTUF7 4f9TjP68WqBu8FGhG8RF0GT0hP6qm4vilQSFQbsUZcxPqJewX6bz51IO8BoSJTXI DawDLbhT44hz9VzN5Xb3WGaKQUcXwwQoBdc7K/sbmpcMv/Nntecpo/+N1kCM65qB ZHQpTt/UrqfFr2NTFrjQ =cYvR -----END PGP SIGNATURE----- --U3BNvdZEnlJXqmh+--