Shouldn't publicly stated security changes prompt a rather quick release? #3462
Answered
by
DavidXanatos
bastik-1001
asked this question in
Q&A Feedback
-
The changelog lists a FIXED SECURITY ISSUE ID, but there was no release of any kind shortly after. Shouldn't there be a release, shortly after something that got a SECURITY ISSUE ID got fixed? Is that purely due to the low severity (which I just assume to be low)? |
Beta Was this translation helpful? Give feedback.
Answered by
DavidXanatos
Nov 28, 2023
Replies: 1 comment 1 reply
-
As noted in the release notes for 1.12.2 there is a signed release 1.12.3 scheduled for the end fo the week, i want first to ensure all the changes in 1,12,2 do not cause any issues. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
bastik-1001
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As noted in the release notes for 1.12.2 there is a signed release 1.12.3 scheduled for the end fo the week, i want first to ensure all the changes in 1,12,2 do not cause any issues.