I am on it. Do not worry just I need to navigate among other things I do. -- Michele Sciabarra mich...@sciabarra.com
----- Original message ----- From: Dominic Kim <style9...@gmail.com> To: dev@openwhisk.apache.org Subject: Re: golang versions / end of life Date: Sunday, July 26, 2020 2:18 AM Mike. So you want to work on it as you already have worked on it? Then I would work on another thing because I need to work on it from scratch if I take that. -Dom 2020년 7월 26일 (일) 오전 1:11, Michele Sciabarra <mich...@sciabarra.com>님이 작성: > Actually I had it working since a while... > > But the annoying part was update examples AND document :D > > -- > Michele Sciabarra > mich...@sciabarra.com > > ----- Original message ----- > From: Carlos Santana <csantan...@gmail.com> > To: dev@openwhisk.apache.org > Subject: Re: golang versions / end of life > Date: Saturday, July 25, 2020 5:25 PM > > Michele > > You mean the new gomod support? That would be RAD ! > > - Carlos Santana > @csantanapr > > > On Jul 25, 2020, at 5:16 AM, Michele Sciabarra <mich...@sciabarra.com> > wrote: > > > > I can do it... I also can update the runtime to add module support. > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > ----- Original message ----- > > From: Dominic Kim <style9...@gmail.com> > > To: dev@openwhisk.apache.org > > Subject: Re: golang versions / end of life > > Date: Friday, July 24, 2020 3:08 AM > > > > Thank you for your efforts. > > Regarding upgrading the go version, I would work on it. > > > > -dom > > > > > > 2020년 7월 23일 (목) 오후 10:19, David P Grove <gro...@us.ibm.com>님이 작성: > > > >> > >> > >> Currently our openwhisk-runtime-go supports golang 1.11 and golang 1.12. > >> Unfortunately, go is now on version 1.14 and has a 2 version EOL policy > >> [1]. So golang 1.11 and 1.12 are out of support and no longer receiving > >> vulnerability fixes. > >> > >> A few weeks back, I had proposed doing a runtime release wave [2] to > pick > >> up security fixes. But I think we really should refresh our runtime-go > >> versions before we do that (as the go version flows through as the > >> actionloop runtime for many of the other runtimes). > >> > >> Does anyone have the time to look at updating runtime-go to go 1.14? > I'd > >> be tempted to skip golang 1.13 unless there was a reason to include it. > >> > >> --dave > >> > >> [1] https://endoflife.date/go > >> > >> [2] > >> > >> > https://lists.apache.org/thread.html/r208d84ea92debcedb80c30895c53397db12989286a787f037e0a5add%40%3Cdev.openwhisk.apache.org%3E > >> > >> >