From dev-return-26256-archive-asf-public=cust-asf.ponee.io@spark.apache.org Thu Oct 25 04:53:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 06AFC180638 for ; Thu, 25 Oct 2018 04:53:07 +0200 (CEST) Received: (qmail 62691 invoked by uid 500); 25 Oct 2018 02:53:06 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 62677 invoked by uid 99); 25 Oct 2018 02:53:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2018 02:53:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6E293C0878 for ; Thu, 25 Oct 2018 02:53:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.989 X-Spam-Level: * X-Spam-Status: No, score=1.989 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=clearstorydata-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id DTkMOu05CZSf for ; Thu, 25 Oct 2018 02:53:04 +0000 (UTC) Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B38865F118 for ; Thu, 25 Oct 2018 02:53:03 +0000 (UTC) Received: by mail-lf1-f45.google.com with SMTP id q6-v6so4833725lfh.9 for ; Wed, 24 Oct 2018 19:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clearstorydata-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FjDWrBSiu5uUOUmYmjNNU2mVRxdVk9Yy6OmPV/08j48=; b=UpQx1lzJ4aJ7C17CykYDB1eJMaxMW3N2lYb576wjjshP5aTbMrdSAfC3a7/+2t3vC2 ir1VXsN/LvAaL/jTZN7YkfwGlZ62cE/y33PjZQTbYp3B5qpRDg9Gu0Pki6Mg8V5gojF1 KSSxMBZ3gBHn5I5jodQB/a4ExVxp/8AXA6ZN5gMxvrIiZGsN2VWQd/4aoeHCrqhkGty8 zTfFTbmNPZIbrO5/9LaWjlava40m1tdlK8WtKL89cm6djvlbOXyU9jjch/xWXD4O9VtH SRfjRcdncfoZGGswPl1YJ+VIo8xxuYQ2u5ONE/VN83wRg8xjDpjP9ulEwJZ0/YcOeaWI aDug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FjDWrBSiu5uUOUmYmjNNU2mVRxdVk9Yy6OmPV/08j48=; b=m4ueHfPdFJhKmfxMypnTO0Lmx0bVW50y4vyfqpzUo+TgA/ObWvt2+MCkB7IQ8eS2ek Y9Qp1A1z/4nCwZ/Ihehj0SHwpx6F7SzLo+qydA5pXYTlfVWo43stWzrYNxeJyK51V8hj eT0fJz5Mld5NMI6Gb0khZKjZFzWvNRjQVBAxSvrYy5C9GDfiCjt6nWnRCzNDmbN8DkkO Kt2UvF/peJfLj4MYfb1N0XcFLC+2aWUfk/EDG30tUU2ouNPRetxraO+iZKIj4h8rPM7Z p+dWe0QtC1DsbtCjVUicOEGOXDVQ3PY0AKCyd6MLnW4Fhk+vxK2dnDeOH+9U5GQ1pJ7Y jRAQ== X-Gm-Message-State: AGRZ1gIsDMp+F8AxznvJyB4TmJmwvDEwQShNuh3oc1TfX4T/5a/Jzbxx ziTXKs9s2NRjGAVXvCZ3cJdyADdB7WmcROS9HSlW0g== X-Google-Smtp-Source: AJdET5c+21K5k9XfBj2nc0P54Dwan9f+XNkb/O1pqluCiLlQGgzYwFz+OVQ4z912tvIKxV0IjDR/5GVZeY+phJMdtNc= X-Received: by 2002:a19:1202:: with SMTP id h2mr158351lfi.122.1540435982048; Wed, 24 Oct 2018 19:53:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mark Hamstra Date: Wed, 24 Oct 2018 19:52:50 -0700 Message-ID: Subject: Re: What's a blocker? To: Saisai Shao Cc: Hyukjin Kwon , Sean Owen , dev Content-Type: multipart/alternative; boundary="0000000000008273c6057904b374" --0000000000008273c6057904b374 Content-Type: text/plain; charset="UTF-8" Yeah, I can pretty much agree with that. Before we get into release candidates, it's not as big a deal if something gets labeled as a blocker. Once we are into an RC, I'd like to see any discussions as to whether something is or isn't a blocker at least cross-referenced in the RC VOTE thread so that PMC members can more easily be aware of the discussion and potentially weigh in. On Wed, Oct 24, 2018 at 7:12 PM Saisai Shao wrote: > Just my two cents of the past experience. As a release manager of Spark > 2.3.2, I felt significantly delay during the release by block issues. Vote > was failed several times by one or two "block issue". I think during the RC > time, each "block issue" should be carefully evaluated by the related PMCs > and release manager. Some issues which are not so critical or only matters > to one or two firms should be carefully marked as blocker, to avoid the > delay of the release. > > Thanks > Saisai > --0000000000008273c6057904b374 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yeah, I can pretty much agree with that. Before we get int= o release candidates, it's not as big a deal if something gets labeled = as a blocker. Once we are into an RC, I'd like to see any discussions a= s to whether something is or isn't a blocker at least cross-referenced = in the RC VOTE thread so that PMC members can more easily be aware of the d= iscussion and potentially weigh in.

On Wed, Oct 24, 2018 at 7:12 PM Saisai Shao <sai.sai.shao@gmail.com> wrote:
Just my two cents of the p= ast experience. As a release manager of Spark 2.3.2, I felt significantly d= elay during the release by block issues. Vote was failed several times by o= ne or two "block issue". I think during the RC time, each "b= lock issue" should be carefully evaluated by the related PMCs and rele= ase manager. Some issues which are not so critical or only matters to one o= r two firms should be carefully marked as blocker, to avoid the delay of th= e release.

Thanks
Saisai
--0000000000008273c6057904b374--