Thanks for starting the discussion. Would be great to see a new release of the core system!
On 2023/02/15 19:43:19 Brendan Doyle wrote: > > Now, I would like to open the floor if there's any low hanging fruit that > we would like to take the opportunity to remove by having a new major > release. I.e. are there any deprecated runtimes default bundled in with the > release that we would like to remove entirely from the repo, changing any > defaults, etc? > We should push out releases of all the runtimes so we have current versions. When we make a core release, one of the things we do on the release branch is replace the "nightly" tag with specific versions in runtimes.json. For most of the runtimes, this is straightforward. We just need to tidy them up and do our usual release wave. I can start things with Go this week. Our default "blackbox" runtime is also very old (based on the past-EOL Python 3.6. We need to either update this to a modern Python version or switch to an actionloop based blackbox runtime. For Ruby and Rust it is less clear what to do. Neither of our runtimes for these languages corresponds to a currently supported version of the language. Our runtime-ruby is at Ruby 2.6 which was EOL in March 2022. Our runtime-rust is at Rust 1.34, which is years behind (and not helped by Rust not doing LTS releases as a matter of project policy). I think we need someone from the community to do a refresh to a modern language version, or we need to drop support for them. --Dave
