You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by Duy Nguyen <du...@gmail.com> on 2017/08/28 11:19:27 UTC
Release for OpenWhisk
Hi -
In the previous tech interchange session we talked about creating releases
for OpenWhisk. It was an interesting discussion and I would follow up here.
I started with a wiki page with some initial ideas for doing releases based
on what we have for now.
https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Release+Process
It basically takes a step forward from the docker image releases [1] that
Carlos has automated recently. In addition to versions from git commits, we
could create a semver tag in GitHub and tag the relevant Docker hub images
with the same version. Current images from the main repo are: controller,
invoker, and action containers.
There are extended discussions about releasing finer-grained artifacts by
publishing jars with maven, SPI plug-ins, etc. (more details at [2]).
However, as this involves major effort to integrate SPIs, more tooling and
so on, how about start creating releases using the early approach with
Docker images, and later add more stuff as the project evolves?
In general, pushing for creating releases will help to ease deployment
management, issue reporting / debugging, and is needed for apache
graduation.
Look forward to seeing your comments.
Thanks,
Duy
[1] https://hub.docker.com/u/openwhisk/
[2]
https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+Interchange+-+Meeting+Notes
Re: Release for OpenWhisk
Posted by Sergio Fernández <wi...@apache.org>.
Then please, adap ASAP that wiki page to the Apache release process.
On Tue, Sep 5, 2017 at 1:24 AM, Bertrand Delacretaz <bd...@apache.org>
wrote:
> Hi,
>
> On Mon, Aug 28, 2017 at 1:19 PM, Duy Nguyen <du...@gmail.com>
> wrote:
> > ...I started with a wiki page with some initial ideas for doing releases
> based
> > on what we have for now.
> > https://cwiki.apache.org/confluence/display/OPENWHISK/
> OpenWhisk+Release+Process
> ...
>
> Note that there is a defined process for Apache releases, you cannot
> just tag stuff and upload to some binary distribution service.
>
> There's more information at
> http://www.apache.org/legal/release-policy.html ,
> http://www.apache.org/dev/release-distribution.html and
> http://incubator.apache.org/guides/releasemanagement.html
>
> -Bertrand
>
Re: Release for OpenWhisk
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Mon, Aug 28, 2017 at 1:19 PM, Duy Nguyen <du...@gmail.com> wrote:
> ...I started with a wiki page with some initial ideas for doing releases based
> on what we have for now.
> https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Release+Process
...
Note that there is a defined process for Apache releases, you cannot
just tag stuff and upload to some binary distribution service.
There's more information at
http://www.apache.org/legal/release-policy.html ,
http://www.apache.org/dev/release-distribution.html and
http://incubator.apache.org/guides/releasemanagement.html
-Bertrand
Re: Release for OpenWhisk
Posted by Carlos Santana <cs...@gmail.com>.
Agree with Sergio,
We have to do a source release first, make sure it follows Apache release
policy, vote on it and then publish the source under Apache dist location
On Mon, Aug 28, 2017 at 10:40 PM Sergio Fernández <wi...@apache.org> wrote:
> I'd love to see OpenWhisk moving forward on releasing. But, with no
> intention to interfere in the technical stuff, just have in mind that any
> kind of artifact tagged with a release version must be voted according
> Incubator rules.
>
> On Aug 28, 2017 04:19, "Duy Nguyen" <du...@gmail.com> wrote:
>
> > Hi -
> >
> > In the previous tech interchange session we talked about creating
> releases
> > for OpenWhisk. It was an interesting discussion and I would follow up
> here.
> >
> > I started with a wiki page with some initial ideas for doing releases
> based
> > on what we have for now.
> > https://cwiki.apache.org/confluence/display/OPENWHISK/
> > OpenWhisk+Release+Process
> >
> > It basically takes a step forward from the docker image releases [1] that
> > Carlos has automated recently. In addition to versions from git commits,
> we
> > could create a semver tag in GitHub and tag the relevant Docker hub
> images
> > with the same version. Current images from the main repo are: controller,
> > invoker, and action containers.
> >
> > There are extended discussions about releasing finer-grained artifacts by
> > publishing jars with maven, SPI plug-ins, etc. (more details at [2]).
> > However, as this involves major effort to integrate SPIs, more tooling
> and
> > so on, how about start creating releases using the early approach with
> > Docker images, and later add more stuff as the project evolves?
> >
> > In general, pushing for creating releases will help to ease deployment
> > management, issue reporting / debugging, and is needed for apache
> > graduation.
> >
> > Look forward to seeing your comments.
> >
> > Thanks,
> > Duy
> >
> > [1] https://hub.docker.com/u/openwhisk/
> > [2]
> >
> https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+
> > Interchange+-+Meeting+Notes
> >
>
Re: Release for OpenWhisk
Posted by Sergio Fernández <wi...@apache.org>.
I'd love to see OpenWhisk moving forward on releasing. But, with no
intention to interfere in the technical stuff, just have in mind that any
kind of artifact tagged with a release version must be voted according
Incubator rules.
On Aug 28, 2017 04:19, "Duy Nguyen" <du...@gmail.com> wrote:
> Hi -
>
> In the previous tech interchange session we talked about creating releases
> for OpenWhisk. It was an interesting discussion and I would follow up here.
>
> I started with a wiki page with some initial ideas for doing releases based
> on what we have for now.
> https://cwiki.apache.org/confluence/display/OPENWHISK/
> OpenWhisk+Release+Process
>
> It basically takes a step forward from the docker image releases [1] that
> Carlos has automated recently. In addition to versions from git commits, we
> could create a semver tag in GitHub and tag the relevant Docker hub images
> with the same version. Current images from the main repo are: controller,
> invoker, and action containers.
>
> There are extended discussions about releasing finer-grained artifacts by
> publishing jars with maven, SPI plug-ins, etc. (more details at [2]).
> However, as this involves major effort to integrate SPIs, more tooling and
> so on, how about start creating releases using the early approach with
> Docker images, and later add more stuff as the project evolves?
>
> In general, pushing for creating releases will help to ease deployment
> management, issue reporting / debugging, and is needed for apache
> graduation.
>
> Look forward to seeing your comments.
>
> Thanks,
> Duy
>
> [1] https://hub.docker.com/u/openwhisk/
> [2]
> https://cwiki.apache.org/confluence/display/OPENWHISK/2017-08-16+OW+Tech.+
> Interchange+-+Meeting+Notes
>