+1 to Dave's opinion. And thank you Mike for all your efforts.
-dom 2020년 8월 25일 (화) 오후 10:55, David P Grove <gro...@us.ibm.com>님이 작성: > > Thanks for all the work on this Michele! > > "Michele Sciabarra" <mich...@sciabarra.com> wrote on 08/24/2020 04:30:52 > PM: > > > > In the Go runtime it was mentioned in a comment that versions of go > > before 1.15 are unsafe. > > What is exactly the problem? Should we then drop runtimes for go > > from 1.11 to 1.14? > > My advice would be that we skip 1.14. We also drop the support for 1.11 > and 1.12 as being past their end-of-life. > > We do a release of openwhisk-runtime-go that supports go 1.13 and go 1.15. > We could omit go 1.13, but I believe it is harmless to include it since the > work is already done and the problems that Matt raised are specific to go > 1.14. Some people might find it useful to have an openwhisk-runtime-go > release that supported go 1.13. > > In core openwhisk's runtimes.json, I would suggest only adding go 1.15 > (skip over go 1.13). Go 1.13 is about to go end-of-life, so let's not add a > runtime that we'll just have to remove almost immediately. > > > Whar about the proxies for other languages? They are built with > > older versions of Go, should we change all tbe runtimes that uses > > the go proxy to build with go 1.15? > > As soon as we get an official release of openwhisk-runtime-go with go 1.15, > we can update the proxies for the actionloop based runtime to use go 1.15 > as the builder and the new openwhisk-runtime-go release as the source for > the proxy. I can do the work for this; it's purely mechanical. > > --dave >
