Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE0B110885 for ; Mon, 23 Sep 2013 20:58:08 +0000 (UTC) Received: (qmail 86284 invoked by uid 500); 23 Sep 2013 20:58:06 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 86056 invoked by uid 500); 23 Sep 2013 20:58:05 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 86024 invoked by uid 99); 23 Sep 2013 20:57:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Sep 2013 20:57:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.220.174] (HELO mail-vc0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Sep 2013 20:57:54 +0000 Received: by mail-vc0-f174.google.com with SMTP id gd11so2556358vcb.19 for ; Mon, 23 Sep 2013 13:57:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=mQ42e1OLQu/RSENFBh3cutO/tGXNtjBopn3ZYyhm/m8=; b=dC6EO8EEjKx1F+bq/W11Zg4YtA18xPg44ryXks/YO3rZaU3DhrDPgg254tQ5p7sXSZ 0ggOdnKDONMpCAW1ECVjDRTpCLUtV/j0IG8cE9O4sQPvVc+4j64eI6pB2+jf9LspQu9M 7d12mNeVmD5Gx0BnvtkKDKrd67fPedjop7606LN62mGxRFz5OcJ5ApyiyeLJBnS8CnOw oGi6ynDyIUSu8GFPhyqQfjf86v+5CVVhM9s/JpspouyC+9X3x3uAYGpMjZ4cJVeQUg1V br/wWGagL/I/nuZwnY1a8dflQKYKqiRsYdPxx+DBYWvGpP6tknXG1nh1QLMMQpPBCh4O r0pg== X-Gm-Message-State: ALoCoQlN1Q0ooIYuu53QH+gWxDx/t9imVCFl4EcqUnZY7PMB7gMKwVFN3Lbpr1VhgCyJNy4yJGny MIME-Version: 1.0 X-Received: by 10.58.169.232 with SMTP id ah8mr457407vec.87.1379969853428; Mon, 23 Sep 2013 13:57:33 -0700 (PDT) Received: by 10.58.74.72 with HTTP; Mon, 23 Sep 2013 13:57:33 -0700 (PDT) X-Originating-IP: [206.190.64.2] Date: Mon, 23 Sep 2013 13:57:33 -0700 Message-ID: Subject: KEYS files within source archives From: Marvin Humphrey To: "general@incubator.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org > On Wed, Sep 18, 2013 at 8:25 PM, Dave Brondsema wrote: > >> Do you have a KEYS file posted somewhere besides within the release? Thanks for a good spot and thoughtful observation, Dave. This is worth discussing. MHO: supplying a KEYS file within the source archive is worthless at best. On Wed, Sep 18, 2013 at 9:50 PM, Ted Dunning wrote: > It is in version control as per custom. Drill uses git so it might not be > quite as obvious if you are used to SVN. > > See, for instance, > > https://git-wip-us.apache.org/repos/asf?p=incubator-drill.git;a=blob;f=KEYS;h=205469b84b8bda60fcb87486182d4fb7caf0485d;hb=HEAD There may be precedent but it seems to me that including a KEYS file within a source archive shouldn't be considered a best practice. (For the record, so long as the KEYS file is available from somewhere else safe, I don't think the issue blocks Drill's release candidate.) Now that changes to our distribution area are captured via version control (dist.apache.org), is there any reason to maintain KEYS in the master branch any more? There was talk a while back of transitioning to an LDAP-centric key scheme, but there are flaws with that approach: former RMs who leave the community suddenly causing the key needed for an old release to become unavailable, etc. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org