Following up on this thread, I think with two positive votes and zero
objections, zero problems reported by users on the latest weekly, and
manual verification of the fix (by me) that we can proceed with this
backport. Kris, were you planning on opening a pull request with the
backport to stable-2.361? I think that would be our usual process and
the most ideal way to proceed, but if that is not practical perhaps
Vincent can backport his own pull request. I am available as a last
resort, but I would prefer not to backport this particular change if
possible since I am neither the release lead nor was I involved in
developing the fix.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjreDiHDNAk2dBF0odcbvXKYhMxdS6dnkz_mqf1gqr56_w%40mail.gmail.com.

Reply via email to