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 <[email protected]> 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 <[email protected]> > To: [email protected] > 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 <[email protected]> > 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 > > > > > > >
