Based on all the discussion on a VOTE mail thread, we can go with the release of one module, which the main openwhisk module, for the initial Apache release. I will prepare another VOTE mail separately. Let's close this mail thread, unless someone opposes to release main openwhisk.
Thanks. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com, Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States -----"David P Grove" <gro...@us.ibm.com> wrote: ----- To: dev@openwhisk.apache.org From: "David P Grove" <gro...@us.ibm.com> Date: 06/22/2018 09:39AM Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating +1 --dave Carlos Santana ---06/22/2018 09:23:55 AM---I will take Bertrand's mentorship advice and release 1 module This is just to go thru the ASF releas From: Carlos Santana <csantan...@gmail.com> To: dev@openwhisk.apache.org Date: 06/22/2018 09:23 AM Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating I will take Bertrand's mentorship advice and release 1 module This is just to go thru the ASF release process and voting. To verify that the source code is free from legal problems, and follows all the legal requirements We just need to go thru one round with the IPMC and explain that this is our first practice run to get the go-client 0.9.0 module Stating that this module is part of a larger suite that will come after Not required, but if folks want to test something about the code in the single tgz they can run the go tests (this will compiled and run go unit tests) And then follow with the other 12 modules same version 0.9.0 as their initial version for each module. Take into account we can separate what we communicate to the outside OpenWhisk end user community as a downloadable, deployable openwhisk platform stack. For example I will hold off a blog post and twitter announcement, until we have a full suite of modules blessed/released and in the ASF dist download site, and have a single page on the webstie (openwhisik.apache.org), that end users that want to download and install the serverless platform stack, can go there and and be able to download all the modules and deploy them together, or pick one of the modules if they only need one. --cs On Fri, Jun 22, 2018 at 8:52 AM Rodric Rabbah <rod...@gmail.com> wrote: > > > On Jun 22, 2018, at 8:18 AM, Vincent S Hou <s...@us.ibm.com> wrote: > > > > I mean if only release this go client code, there is nothing we can run > it against. > > And that is entirely fine per all the ASF docs I’ve read. Is there a > requirement that the code must be functional in some extended capacity? > > The ASF docs point out verification steps but none include actually > running anything from what I’ve learned so far. > > I don’t think Bertrand, Rob, or I are saying not to release all 13 but > rather go through with just 1 repository first end to end. > > The Apache motto is release early release often, no? > > -r
