Return-Path: X-Original-To: apmail-hawq-dev-archive@minotaur.apache.org Delivered-To: apmail-hawq-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 6846918FC2 for ; Tue, 29 Sep 2015 10:17:05 +0000 (UTC) Received: (qmail 36242 invoked by uid 500); 29 Sep 2015 10:10:09 -0000 Delivered-To: apmail-hawq-dev-archive@hawq.apache.org Received: (qmail 36194 invoked by uid 500); 29 Sep 2015 10:10:09 -0000 Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hawq.incubator.apache.org Delivered-To: mailing list dev@hawq.incubator.apache.org Received: (qmail 36181 invoked by uid 99); 29 Sep 2015 10:10:09 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2015 10:10:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id ED65EC701E for ; Tue, 29 Sep 2015 10:10:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.315 X-Spam-Level: * X-Spam-Status: No, score=1.315 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, URIBL_BLOCKED=0.001, URIBL_DBL_ABUSE_REDIR=0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id JqtrT5Oi5JNH for ; Tue, 29 Sep 2015 10:09:55 +0000 (UTC) Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [96.114.154.161]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id B7FA52315E for ; Tue, 29 Sep 2015 10:09:54 +0000 (UTC) Received: from resomta-po-14v.sys.comcast.net ([96.114.154.238]) by resqmta-po-02v.sys.comcast.net with comcast id Ny9c1r00558ss0Y01y9nWi; Tue, 29 Sep 2015 10:09:47 +0000 Received: from tinybb.boudnik.org ([24.130.135.131]) by resomta-po-14v.sys.comcast.net with comcast id Ny9m1r00P2qGB6001y9n5k; Tue, 29 Sep 2015 10:09:47 +0000 Received: by tinybb.boudnik.org (Postfix, from userid 1002) id 2CD47978; Tue, 29 Sep 2015 10:12:34 +0000 (UTC) Date: Tue, 29 Sep 2015 03:12:33 -0700 From: Konstantin Boudnik To: dev@hawq.incubator.apache.org Subject: Re: Staying with RTC (review-then-commit) rule Message-ID: <20150929101233.GY19314@boudnik.org> References: <20150928122903.GI19314@boudnik.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Organization: It's something of 'Cos User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1443521387; bh=DzcjdEMgedFn5FRMz6wXLrcVEGF3RO2Gmh7OjizZW/o=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=dV2XrI3uhuiB2gBegs7buXph3LSmFEQZYyiQTzOR+OPqDLDYxIB33kaYgzPa9UUbY u2PQjSXNQTc1g9KxPZ8EOHvEbFQy2CtrS6eVjIqR4XNGFDBfBushOe38fTo6tCVR90 DE6nHqOZNyl30bGT5tYAZaeKeOOle1BFxxu9JvIhanmCzE3B6MO7AB/EQnctG3XNrq j3pHq0iFZ9kCAwnb3eQahwbWPeMaUkS+OLDxheWp7S5mLpTkGYQdWZLTBbUF8HIjmV J+4RiOXphJ8ek4YmfMKQ+KE4yVIkj2o/GPg/66qkFkWfZHD2g1n0GqxHup/905APYB rXBghh93y7qdA== On Mon, Sep 28, 2015 at 11:06PM, CHANG Lei wrote: > CTR (Commit then Review) or RTC (Review then commit) is a process we need > to finalize soon. Actually, most of the hawq code developed before follows > CTR. > > And I just found some other commits on the branch (that does not get 2 +1s, > looks from Caleb :-) > > So IMO, to get this finalized might be a good practice for an apache voting > process on Procedural item (http://www.apache.org/foundation/voting.html). While using voting to rubber-stamp a procedural vote is a legit use of the voting process, let's only use it after the consensus [1] is reached. Voting isn't a replacement nor a right mechanism to establish policies or practices within the community. A couple of good examples of gaining the consensus through the community relevant to the topic are [2] and [3] Cos [1] https://www.apache.org/foundation/voting.html#LazyConsensus [2] http://bit.ly/1gLeArc [3] http://apache-ignite-developers.2346864.n4.nabble.com/Jira-Process-tp1816p1831.html > Most committers do not know about the process. > > Cheers > Lei > > > On Mon, Sep 28, 2015 at 8:45 PM, Caleb Welton wrote: > > > Konstantin, I don't think all the developers are aware of the differences > > between CTR and RTC. Would you care to elaborate on the contribution > > protocols? > > > > Thanks! > > > > > > On Mon, Sep 28, 2015 at 2:29 PM, Konstantin Boudnik > > wrote: > > > > > I am the big advocate of CTR model and has been pushing it in a number of > > > the > > > projects before. However, for the very early ones like Hawq right now, > > RTC > > > might make more sense: it takes time to learn how to add new trusty > > people > > > to > > > the community; also for new committers it helps to learn the code faster > > by > > > doing the mandatory reviews. But before you know it, I will be doing > > rounds > > > here pushing for CTR ;) > > > > > > Cos > > > > > > On Mon, Sep 28, 2015 at 03:11PM, Roman Shaposhnik wrote: > > > > Hi! > > > > > > > > just wanted to say what I said on HAWQ-7, but > > > > since not all of us are watching that JIRA, I think > > > > it would be useful to repeat it here. > > > > > > > > While there's nothing wrong with lazy consensus, > > > > but initially I'd suggest staying with RTC model. > > > > Thus +1 from somebody else should be explicitly > > > > required. > > > > > > > > I don't think there's any disagreement, but I just > > > > wanted to have it explicitly mentioned. > > > > > > > > Thanks, > > > > Roman. > > > > >