Chetan, That is really good to use Apache Maven Staging repo for our release process in future. So far our release tool is openwhisk-release: https://github.com/apache/incubator-openwhisk-release. Either manual or automated mode can push the artifacts into https://dist.apache.org/repos/dist/dev/incubator/openwhisk/.
I was wondering if Maven release can be integrated to current process. Feel free to open an issue and draft the plan. 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 -----Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: ----- To: dev@openwhisk.apache.org From: Chetan Mehrotra <chetan.mehro...@gmail.com> Date: 06/25/2018 06:40AM Subject: Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating > 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 @Vincent Looking at current released artifacts it appears we are only releasing source tars. Going forward we should look into including Maven release of various sub modules in main OpenWhisk repo like openwhisk-common, openwhisk-controller etc as part of vote. Until vote they would be present in Apache Maven Staging repo and post vote they would be publish to global Maven repo. See [1] for reference. Chetan Mehrotra [1] http://www.apache.org/dev/publishing-maven-artifacts.html On Sat, Jun 23, 2018 at 3:09 PM, Bertrand Delacretaz <bdelacre...@apache.org > wrote: > Hi Rodric, > > On Fri, Jun 22, 2018 at 2:52 PM 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?... > > There's no such requirement for a podling release, especially not for > your first Incubator release. > > I would expect that the released module has unit tests that pass when > building it, but that module not being usable in isolation is not a > problem, from the Incubator PMC's point of view. > > Of course the ultimate goal is for OpenWhisk to release fantastic > software, we're not doing all this just to keep "the system" happy ;-) > > But I think "priming the system" as Matt says, by releasing a single > module, will get us there faster and with less effort. > > -Bertrand >
