From dev-return-2194-archive-asf-public=cust-asf.ponee.io@openwhisk.apache.org Thu Jul 12 17:10:10 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 7E815180654 for ; Thu, 12 Jul 2018 17:10:09 +0200 (CEST) Received: (qmail 37540 invoked by uid 500); 12 Jul 2018 15:10:08 -0000 Mailing-List: contact dev-help@openwhisk.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openwhisk.apache.org Delivered-To: mailing list dev@openwhisk.apache.org Received: (qmail 37528 invoked by uid 99); 12 Jul 2018 15:10:07 -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, 12 Jul 2018 15:10:07 +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 51679C032B for ; Thu, 12 Jul 2018 15:10:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.889 X-Spam-Level: * X-Spam-Status: No, score=1.889 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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=gmail.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 4qX1aVUBUqnc for ; Thu, 12 Jul 2018 15:10:06 +0000 (UTC) Received: from mail-yb0-f169.google.com (mail-yb0-f169.google.com [209.85.213.169]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 341145F43B for ; Thu, 12 Jul 2018 15:10:06 +0000 (UTC) Received: by mail-yb0-f169.google.com with SMTP id e9-v6so11524096ybq.1 for ; Thu, 12 Jul 2018 08:10:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=9i+Q8AO5qbCVjgpy2s5WVJnWs98AH+cxIgac3Ar0+IU=; b=dvnPO96QbnuHHKU89JylXTK6sQ5LjkyqIOjaoiPeqGlMgigrCc6UZQLwIk1n8F5ky8 GZ3XWLUXC6Q8r93jU4qH8nuNVnVnqxUzKpnakTNgdX4d4VsexLh7zMw+za+CePPeLKLG t7IJezIbqtbmCeJBcGko0JTc6m1Mfb6HRT90v4TIfrXst72EmBDB/f9edcN/UM2A3NIn xOKONg0m589hUjaC575/MdM14rl8DHPYBGflKYzfHZ9pTy7dQQdfkn4LCwgAsHyrx3tS hVmy70zT5WzEkrcwNRYJMH5xbzVrBcsYamkFd5TDMslFFWe2TPO+gfDGsV9xSZ43s3rx wxJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=9i+Q8AO5qbCVjgpy2s5WVJnWs98AH+cxIgac3Ar0+IU=; b=EusjFM58nI4v2EY+ETmg85TB/7+6sJzdHyGTXxCoIEmJE0xapbYwzsXe2YK56cykhr 9UNHN56ciH1lmszVSVvWW4NYCE9fTvj+052NcR1vkumM06PVIy0Wz3S55RJ3NspEWFFo PZQi9p+T/VuITC61AAXll+IKvafrCf+i9mg4LYZUXagNLs6tenvaJEZ3RCzvfy7BOhIy zXbiW1jS7edejfvNvtrZT59fmMUUZJXPW67Gu1ktU/4StKlVLfv1kzAI7leP2x8azF0t XK7pe9CJYrf/RL8G6bWhRoWkjp9ipiE4t8qNrwhpmodBc3OAy1eY+WJp/8T01sK/QpHg r0AQ== X-Gm-Message-State: AOUpUlFXI1jo9mgQQHIDE2xSfb8zWZGAPRMACtwY8d1U70Is3bvh36p3 HF93TfdU9EG4jOgZu7DL1P8y3k+cx/4/biqO2GD8DA== X-Google-Smtp-Source: AAOMgpdxBgIvDOoNjUWZ18LhPssNwZQ5bYLOne5CLwzXC+71NAlOgjVDFJKql1fiWzsl0/HChB20VHA5V5MRo1YaU8I= X-Received: by 2002:a25:2bc4:: with SMTP id r187-v6mr1319717ybr.377.1531408199947; Thu, 12 Jul 2018 08:09:59 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a81:6b05:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 08:09:19 -0700 (PDT) In-Reply-To: References: <82D40720-6569-421E-847C-3C86EA07BEC1@akrabat.com> <33048D64-865C-48C6-8B4B-84A7162472F7@adobe.com> From: Rodric Rabbah Date: Thu, 12 Jul 2018 11:09:19 -0400 Message-ID: Subject: Re: should we enable signed commits on our github repos? To: dev@openwhisk.apache.org Content-Type: multipart/alternative; boundary="000000000000c39ad60570cec1a6" --000000000000c39ad60570cec1a6 Content-Type: text/plain; charset="UTF-8" Hi Matt, I think the concern is for the runtime repso, and the cli related repos for example: https://github.com/apache/incubator-openwhisk-runtime-nodejs/releases all the runtime repos and the cli have "releases" which are not the same - we used this more as stable builds for dependence management (until we can adopt the official releases). -r On Thu, Jul 12, 2018 at 11:05 AM, Matt Rutkowski wrote: > >>Is there an "OpenWhisk release management" page somewhere already, or > should one be created ? > > That is what the entire release repo. is inclusive of, with the goal of > making it a community-inclusive dynamic process linked to CI/CD > processes... > https://github.com/apache/incubator-openwhisk-release > > open issues, discuss/link in dev list, create PRs... > > > > > > From: Bertrand Delacretaz > To: dev@openwhisk.apache.org > Date: 07/12/2018 09:58 AM > Subject: Re: should we enable signed commits on our github repos? > > > > On Thu, Jul 12, 2018 at 4:47 PM Matt Rutkowski > wrote: > > > > .. thought I was endorsing the Apache release process we have been > working > > on in accordance with Apache policies... did you read into that > statement > > otherwise?... > > Apparently yes, sorry about that...I understood "tagged releases" to > just mean "tagging something on GitHub". > > OTOH some > https://github.com/apache/incubator-openwhisk-*/releases > are > happening which can be confusing - I think the role of those needs to > be clarified (*) at least so that PPMC members know what is what and > don't put themselves at risk. > > Is there an "OpenWhisk release management" page somewhere already, or > should one be created ? > > -Bertrand > > (*) Test releases and nightly builds are ok for Apache projects but > there are some restrictions on how they are advertised, see > http://www.apache.org/legal/release-policy.html#host-rc > > > > > > > --000000000000c39ad60570cec1a6--