Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 64A6B18300 for ; Thu, 4 Feb 2016 20:53:16 +0000 (UTC) Received: (qmail 29330 invoked by uid 500); 4 Feb 2016 20:53:16 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 29284 invoked by uid 500); 4 Feb 2016 20:53:16 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 29267 invoked by uid 99); 4 Feb 2016 20:53:16 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2016 20:53:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 932BD1A035D; Thu, 4 Feb 2016 20:53:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.798 X-Spam-Level: X-Spam-Status: No, score=0.798 tagged_above=-999 required=6.31 tests=[FSL_HELO_BARE_IP_2=1.499, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 10d_bWHi4uGM; Thu, 4 Feb 2016 20:53:13 +0000 (UTC) Received: from relayvx12c.securemail.intermedia.net (relayvx12c.securemail.intermedia.net [64.78.52.187]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id C53B8439AB; Thu, 4 Feb 2016 20:53:12 +0000 (UTC) Received: from securemail.intermedia.net (localhost [127.0.0.1]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by emg-ca-1-2.localdomain (Postfix) with ESMTPS id 0695F53E2F; Thu, 4 Feb 2016 12:53:12 -0800 (PST) Subject: Re: [Announce] Github integration live MIME-Version: 1.0 x-echoworx-msg-id: 3125090e-331d-4ad4-948e-a5925c6d98d5 x-echoworx-emg-received: Thu, 4 Feb 2016 12:53:11.959 -0800 x-echoworx-message-code-hashed: a21a51a87305c35d3ccd88f01cf2991285ff720b789ae05c3283cb23b377fbfb x-echoworx-action: delivered Received: from 10.254.155.17 ([10.254.155.17]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 819; Thu, 4 Feb 2016 12:53:11 -0800 (PST) Received: from MBX080-W4-CO-1.exch080.serverpod.net (unknown [10.224.117.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by emg-ca-1-2.localdomain (Postfix) with ESMTPS id B9D2153E2F; Thu, 4 Feb 2016 12:53:11 -0800 (PST) Received: from MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) by MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 4 Feb 2016 12:53:10 -0800 Received: from MBX080-W4-CO-1.exch080.serverpod.net ([10.224.117.101]) by mbx080-w4-co-1.exch080.serverpod.net ([10.224.117.101]) with mapi id 15.00.1130.005; Thu, 4 Feb 2016 12:53:10 -0800 From: Balu Vellanki Bala To: "dev@falcon.apache.org" CC: "user@falcon.apache.org" Thread-Topic: [Announce] Github integration live Thread-Index: AQHRWld38kpayuTwsU+OYiJFJGA1b58SlFoAgAAvPICACHQLAIABL8oA Date: Thu, 4 Feb 2016 20:53:10 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [184.23.216.210] x-source-routing-agent: Processed Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable Ajay and Team, Patches that are inflight will be committed old way, the new patches will be reviewed and committed via pull request. Hope this is ok, Thanks Balu=20 On 2/3/16, 10:45 AM, "Ajay Yadav" wrote: >Hello everyone, > >Some people are still uploading patches on reviewboard and JIRA. Request >everyone to switch to pull request model. Let me know if you face any >issues. > >On Fri, Jan 29, 2016 at 3:10 PM, Ajay Yadav wrote: > >> Looks like the email per review comment is not yet disabled, I am >> following up with INFRA, sorry for the inconvenience. >> >> On Fri, Jan 29, 2016 at 12:21 PM, Pallavi Rao >> wrote: >> >>> Thanks Ajay for enabling this! Simplifies the whole patch upload, >>>review, >>> commit process. >>> >>> Will start using right away :-). >>> >>> On Fri, Jan 29, 2016 at 11:09 AM, Ajay Yadava >>> wrote: >>> >>>> Hello everyone, >>>> >>>> Good news!! Github integration is complete and ready for use. As part >>>>of >>>> this some more good stuff got done. >>>> >>>> 1. A new tool to merge pull requests has been created. It *squashes >>>> commits*, *reformats the commit messages in standard format*, *adds >>>> reviewers, retains original contributor as author of the commit >>>>*etc. >>>> Usage guide has been made available on wiki >>>> =20 >>>>>>>equests> >>>> . >>>> 2. New merge tool also automates the closure of the relevant JIRA >>>> with fix version. >>>> 3. A pre commit build has also been configured. No more testing >>>> patches on your local box. >>>> 4. How to Contribute guide >>>> =20 >>>> >>>>has >>>> been updated with several new sections for non code contributions >>>>and >>>> github pull request model. >>>> 5. README file has been updated. It now parses markdown >>>>syntax(looks >>>> lot better in github now) and contains the link to how to >>>>contribute guide, >>>> change log etc. >>>> >>>> *How it works?* >>>> With the new integration in place, whenever a new pull request is >>>> created, a pre commit build will be automatically triggered and >>>>result will >>>> be displayed along with the "conflict status"(see attachment). >>>> >>>> Also every time a pull request *which contains JIRA id* is created asf >>>> bot puts these details in the corresponding JIRA. See FALCON-1770 >>>> for an example. >>>> >>>> To avoid noise on the mailing list we have disabled the emails >>>>whenever >>>> a comment is made on the pull request. You should watch the >>>>repository and >>>> use github notifications to see all updates. >>>> >>>> *Key things to take care of for pull requests*: >>>> >>>> - Mention JIRA id in your pull request see this pr >>>> for reference >>>> - Don't forget to update the CHANGES.txt >>>> - You *don't need* to squash commit messages, but please make >>>> meaningful commit messages for each update. >>>> >>>> >>>> I will recommend all contributors to start using the new pull request >>>> method so that they are reflected as the author of their >>>>contributions in >>>> the github/git. >>>> >>>> *[image: Screen Shot 2016-01-23 at 11.45.02 PM.png]* >>>> >>>> Cheers >>>> Ajay Yadava >>>> >>> >>> >>> _____________________________________________________________ >>> The information contained in this communication is intended solely for >>> the use of the individual or entity to whom it is addressed and others >>> authorized to receive it. It may contain confidential or legally >>>privileged >>> information. If you are not the intended recipient you are hereby >>>notified >>> that any disclosure, copying, distribution or taking any action in >>>reliance >>> on the contents of this information is strictly prohibited and may be >>> unlawful. If you have received this communication in error, please >>>notify >>> us immediately by responding to this email and then delete it from your >>> system. The firm is neither liable for the proper and complete >>>transmission >>> of the information contained in this communication nor for any delay >>>in its >>> receipt. >> >> >>