That is great news Dave! Thanks for all your diligence in getting to this point.
My only ask would be to update the table (README) in the release repo. https://github.com/apache/incubator-openwhisk-release and the automation JSON: https://github.com/apache/incubator-openwhisk-release/blob/master/tools/config.json to include an entry (with hash of commit) for this new repo. In addition, I would appreciate it if you could follow the release process/steps there and open any issues you find with the exiting documentation (when following the manual process or auto. process), i.e., "instructions for release managers ( https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md ). Of course, Vincent is the "go to" person for questions on docs/process Cheers to you! -Matt From: "David P Grove" <[email protected]> To: [email protected] Date: 10/23/2018 10:40 AM Subject: towards the first apache release of openwhisk-composer Now that the formal donation process for the composer code base is completed, we can start working towards the first formal release of composer from the Apache OpenWhisk. The motivation for a formal release is that we should have a formal Apache release to enable us to publish an openwhisk-composer package to npm (to replace the prior ibm-functions/composer npm package). I'm willing to act as release manager for the initial release of this package. I believe the main technical work to be done before we can start preparing a release candidate and then initiating the voting process is to agree on the npm package name (suggestion: openwhisk-composer), and update the documentation/code in the openwhisk-composer code base accordingly. Are there any other items that I have overlooked? --dave
