Regarding whether there was demand for the runtime, I was actually thinking it'd be better to make the runtime available before we know of someone in particular wanting to use it. Right now, the OpenWhisk site shows that we don't have the latest runtimes for a few of the platforms we support, like dotnet and ruby. I was thinking about this from the perspective of someone encountering OpenWhisk for the first time. They might see the lack of the latest version of their preferred platform and think "Oh, OpenWhisk must be dead by now. I'll go use x." Having the latest versions available would dispell this misconception.
As an example, when I encountered OpenWhisk in 2018 and started trying it out, I thought of it as being an alive project. When I revisited it recently, I saw the lack of up to date runtimes and I was under the impression the community was winding down in favor of more modern projects like Knative. I dug a bit deeper though and found that there was still a lot going on. On Tue, Apr 20, 2021, 11:35 AM Matt Rutkowski <mrutkow...@apache.org> wrote: > Hi Matt, > > I do not recall that discussion (and cannot easily locate it myself), but > my belief is that support for non-LTS versions of languages in our runtimes > in general is primarily a consideration of our community's ability to in > turn support it. I am for supporting all major versions of popular > languages as long as we have a dedicated member of our OW project to > support it. > > I have not coded anything using .NET for over 10 years so have no idea > which versions are popular by app. devs. and would defer to your > testimonial that it has value. After all, the owners of a language decided > to produce a major release for a reason with functionality some target > audience viewed as valuable. > > It is more than fair to reopen the discussion and discuss the possibility > if we can be given a strong case for a target audience that would use OW on > that version (and not be able or willing to upgrade to an LTS version). > Plus, we would likely need to be assured that we have a champion(s) to > support that version if issues come in. > > -MR > >
