[GitHub] paulcastro commented on issue #277: Add support for Swift version 3.1.1 "kind"

[gi...@git.apache.org]

paulcastro commented on issue #277: Add support for Swift version 3.1.1 "kind"
URL: https://github.com/apache/incubator-openwhisk-wskdeploy/issues/277#issuecomment-305883409
 
 
   The semantics may be changing. In the past, minor and patch level changes to Swift were just updates to the major version kind.  This meant that, for example, 2.0.1 would replace 2.0.0 and the kind `swift:2` (actually the label was `swift`) would not change.
   
   We now have to retain binary level compatibility so even patch level changes will create a new kind.  Right now we support `swift:3` and very soon `swift:3.1.1`, with `swift:4.0.0` just around the corner.
   
   This means the nature of `swift:default` is likely going mean "whatever the latest stable version" is.  @rabbah and @bjustin-ibm suggested using `swift:latest` instead of `swift:latest`.  It may also make sense to have `swift:development` that points to some relatively stable version of a Swift alpha or beta release.
   
   What does deprecation really mean? I think the latest thought on this is that we don't have to remove a kind when we deprecate it.  It will just mean its no longer supported and we won't test it anymore. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services