To help with the confusion I try to clean up the "releases" github pages
for both CLIs wsk and wskdeploy

https://github.com/apache/incubator-openwhisk-wskdeploy/releases
https://github.com/apache/incubator-openwhisk-cli/releases

The tag "latest" means nightly and is mark in red as "pre-release"
Apache OpenWhisk Releases right now should be tag as x.y.z-incubating and
is mark in green "latest-releaes"

Any tags with `x.y.z` this are old before we cut the first Apache OpenWhisk
release.

One weird thing I found was in wskdeploy there is a 0.9;9 and
0.9.8-incubating, I left 0.9.9 just in case someone is using the convenient
binaries
Can't remember if I created that tag or someone else.
But it would not matter that much if we cut another release of the CLIs
soon, and then we can delete this 0.9.8 binaries






On Wed, Dec 12, 2018 at 12:03 AM Bertrand Delacretaz <bdelacre...@apache.org>
wrote:

> Hi Matt,
>
> On Tue, Dec 11, 2018 at 7:32 PM Matt Rutkowski <mrutk...@us.ibm.com>
> wrote:
> > ...https://github.com/apache/incubator-openwhisk-website/pull/353 ...
>
> Thank you very much for this. I like it, with a few minor comments.
>
> I'd prefer saying "Apache Releases" or "Apache OpenWhisk Releases"
> instead of "Official Releases".
>
> It would be good to link to
> http://www.apache.org/legal/release-policy.html somewhere, to provide
> background information.
>
> > In some special cases, Committers on the project may choose to use
> > GitHub to tag certain builds...
>
> Does that automatically cause those builds to appear as releases like
> at https://github.com/apache/incubator-openwhisk-wskdeploy/releases ?
> If not, GitHub tags are perfectly ok of course, but I think the mix of
> Apache Releases and tagged builds there is a major source of confusion
> and should be avoided.
>
> I would expect tags to appear only at (for example)
> https://github.com/apache/incubator-openwhisk-wskdeploy/tags - and
> document tag naming conventions might be useful for clarity if there
> are none so far.
>
> -Bertrand
>


-- 
Carlos Santana
<csantan...@gmail.com>

Reply via email to