-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.8.3: what do we want to include? #3781
Comments
Push to future version:
Other stuff should be worked on and merged. |
Yep. 1.8.3 was the version that programmed to dump nodejs 8 support. Sticking to that. |
Is it possible to have a release that only fixes the critical, security bugs, and doesn't do the entire nodejs migration? The reason I ask is because those fixes seem important to get out there quickly, and combining those with the nodejs migration will make it harder for us to deploy the new version. Thanks! |
What do you mean by "entire nodejs migration"? :D |
@micah, starting from 2020, nodejs 8 is not supported by its developer (https://nodejs.org/en/about/releases/). The deprecation has been in the roadmap for quite a long time. Moving to a different node version is really easy, if you are ok using the binary release from https://nodejs.org/en/download/ instead of your distro's. It's really unzipping a tarball and putting a symlink to |
Closing this ticket. The missing items for the release are being tracked in the 1.8.3 milestone. |
We have done a lot of work lately, thanks to @JohnMcLear that came back with all his energy (many thanks, John).
It is time to start thinking about a release.
There are still a lot of PRs & issues outstanding, and before we cut a new release, we need to select what to include and what to leave behind.
My proposal is:
Let's review the milestone for 1.8.1 and include there all the PRs / issues that we want to integrate, and move to 1.8.2 everything that we decide to leave out.
The text was updated successfully, but these errors were encountered: