-
Notifications
You must be signed in to change notification settings - Fork 534
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
new release: 1.8.1 is due on March 13, 2019 #277
Comments
The (minuscule) libssh2 security team got several security issues reported a while ago and we've been busy working on fixes to them as well as working on the documentation and coming advisories etc which has put a little dent in the release planning for the next release. I think we all are ready for a release but it felt unnecessary to stress one out that doesn't have these issues fixed now that we are aware of them. I should hope that we get control of the situation and can offer a new release soon. Please bear with us. |
Thanks for the update, much appreciated! |
Is there any update on this? Just curious on a ruff timeline to be expected. |
Even if it is several already reported issue on fixing each one would be good to make new release. |
any update on this? |
I promise that you will notice when there is one. |
Thank you, it is live now |
Yes, but @willco007 decided to only do a 1.8.0 + security-fixes branch so 1.8.1 contains no other fixes than that... So I will suggest we make a 1.9.0 release from master asap. |
We have the second half of the security fixing on master in a PR but we are cleaning up a bit more in that commit before taking it. Should be landed by EOD. |
1.8.1 has been released. A 1.9.0 release is now discussed on the mailing list. |
Is there any update for a 1.9.0 release? The last thing I saw in the mailing list was a loose plan to release 1.9.0 on April 11th, but I haven't seen anything since. |
Would you mind releasing a new drop and I'll update the Buildroot package to use this version for the upcoming LTS release?
The text was updated successfully, but these errors were encountered: