Hi Ron, Thanks for the reply.
Based on the current nature of openwhisk, all the 13 repos/modules are working together. If we only release one module, for example, the client go(go sdk) as suggested, it is a purely client tool, which needs the openwhisk service running, in order to run against. If there is only this client go(go sdk) offered to ASF incubator with no other components, how can they verify the functionality? If they have no idea whether it works correctly, how could this initial go sdk get passed, unless you have a different opinion? This is my concern to merely release one for the first time. All the modules by far need to run as complete platform. We have openwhisk offering the service, client go, cli and other tools as the client to access them. We need to have different runtimes to make sure openwhisk supports. It is like a FIFA World CUP team, which needs 11 players to field in order to play. To make life easier, I can consolidate all the modules into tar and come up with a instruction and scripts to make installation and verification explained. Folks can download it only once, read the instructions, run the scripts as needed, and bingo. What do you think?? 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 -----Rob Allen <r...@akrabat.com> wrote: ----- To: dev@openwhisk.apache.org From: Rob Allen <r...@akrabat.com> Date: 06/22/2018 01:46AM Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating > On 22 Jun 2018, at 05:14, Vincent S Hou <s...@us.ibm.com> wrote: > > Great thanks to folks with votes and the comments. Wow, a lot happened on my travel day! > As a recap of current replies we have received, we have opened a list of > issues to be fixed for OpenWhisk in the coming release or further releases: I’m happy with items 1-5. As long as the ASF incubator people are happy with a release that doesn’t have the org.apache.openwhisk.* package name, it all seems fine. > Regarding how many repositories we are going to release, we decided to > continue with the release of 13 repositories, after my discussions with many > OpenWhiskers. All the 13 repos by far are great intelligent assets, which > have been evolving during the past months or even years. FWiW, I strongly disagree with this. Bertrand took a fairly cursory look over the first attempt at a release and came up with a laundry list of items to be addressed - none of which were related to the operation of the code itself or even the build process. It’s reasonable to assume that when it goes to the Incubator people, they are going to have another list of items to address that are again nothing to do with the operation of the code. It seems to me that it would be much easier and *polite* to get all the way through to a release tarball on the Apache servers with a single component that’s reasonably easy for the Incubator people to assess and check that we’ve got everything right. It really doesn’t matter what it is as it’s all about the release process details. Rodric suggested wskdeploy or the GoSDK. Either would work really well as they are small and easily buildable. I see no reason why once we successfully get the first tarball onto the Apache servers, we can’t start rolling the “big” product (the 13 inter-related tarballs) the following day as 0.9.1. If we really want 0.9.0 to be the full caboodle, then, we can do the “get-our-ducks-in-row” release of wskdeploy as 0.8.0. Regards, Rob -- (“-ra” just looks wrong!)
