Hi Rodric, A group means nothing else but to release them together. We can put any two or few projects together as a GROUP. We still release separate tar files, even if they are in a group. Like in the mail thread for client go and cli, we still release two artifacts: The source code artifact of openwhisk client go can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz
The source code artifact of openwhisk cli can be found at: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz but they are in a GROUP. The reason I want to group them is to avoid sending out 13 mail for votes. Instead, I only need to send out 5 or 6. Don't get it complicated. A GROUP is just a group, which does not mean the items have any interaction or mixture. Best wishes. Vincent Hou (侯胜博) Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: [email protected], Phone: +1(919)254-7182 Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States -----Rodric Rabbah <[email protected]> wrote: ----- To: [email protected] From: Rodric Rabbah <[email protected]> Date: 08/04/2018 09:47AM Subject: Re: [DISCUSSION]: Release plan of OpenWhisk 0.9.0 for all modules Hi Vincent, what do you mean by a group - is it a single tar ball that includes a directory for each git repository? without knowing specifically what you mean by a group, the following may not make sense but - catalog and apigatway should be orthogonal - can you explain the logic behind coupling them - wskdeploy and kube deploy also orthogonal (one is user facing the other operator facing) - we should include the compose deployment (if we group compose and kube together, that makes more sense to me) - docker, python and swift as a group might make more sense since the latter depend on docker image - nodejs, java, php (eventually ruby and ballerina) are all independent runtimes -r On Fri, Aug 3, 2018 at 11:42 AM, Vincent S Hou <[email protected]> wrote: > Hi all, > > In order to keep you on the same page, I will discuss my release plan for > openwhisk 0.9.0 of all the 13 modules. > > As you know, we have already released OpenWhisk main module for Version > 0.9.0 in Apache for the first time. There are still 12 other > modules/projects on the roadmap. I would like to release the rest of them > in groups: > > * client go and cli as a group, > * catalog and apigateway as a group, > * wskdeploy and deploy cube as a group, > * Nodejs, Java and Swift runtimes as a group, > * Docker, Php and Python as a group, > > till all the modules are released under 0.9.0, which means I will send out > emails for votes based on different groups. Please prepare for them. I > expect another month to release all the rest modules, on top of main module. > > I will tag all of them as Version 0.9.0-incubating to be consistent with > the main module, so far in the end we will have all the 13 modules under > the same version number for users to pick, build and install. > > I also offer a full-set artifact named openwhisk-0.9.0-incubating-all.tar.gz > including all the 13 modules for one-stop download, after all the 13 > modules are released. > > The reason why we would not release all the modules at a time was > discussed here:https://www.mail-archive.com/[email protected]/m > sg01893.html. This release plan I proposed above is a compromise of > release all at a time and release one-by-one. I would like to hear the > comments from about this release plan. If no objection is received, we will > go with it. > > Thank you. > > Best wishes. > Vincent Hou (侯胜博) > > Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM > Cloud > > Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: [email protected], > Phone: +1(919)254-7182 > Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United > States > >
