openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chetan Mehrotra <>
Subject Re: [VOTE] Release Apache OpenWhisk 0.9.0-incubating
Date Mon, 25 Jun 2018 10:40:27 GMT
> 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

On Sat, Jun 23, 2018 at 3:09 PM, Bertrand Delacretaz <
> wrote:

> Hi Rodric,
> On Fri, Jun 22, 2018 at 2:52 PM Rodric Rabbah <> wrote:
> > > On Jun 22, 2018, at 8:18 AM, Vincent S Hou <> 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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message