I will likely miss the beginning of the Governance meeting today unless my plane lands super-fast. My vote: I agree that the issue is serious enough to delay the release.
My proposal would be to spin 3.10.1 only with this fix. In such case we could delay LTS release till Friday and do some spot-checks of the new RC candidates with the fix. 2017-09-13 15:39 GMT+01:00 Daniel Beck <m...@beckweb.net>: > > > On 13. Sep 2017, at 16:06, Jesse Glick <jgl...@cloudbees.com> wrote: > > > > IIUC we can simply patch the image to either have a writable `$HOME`, > > or specify an explicit `-workDir`, so that most users are not > > affected—right? > > > > Right now, I don't think 2.73.1 is ready for release due to this issue. We > _really_ need this fixed before we publish 2.73.1. Otherwise it will just > not be usable in any serious environment. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-dev/uv2SG7k2log/unsubscribe. > To unsubscribe from this group and all its topics, 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/C8769C58-4123-4ED6-A8AB-986AD2CA75E1%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPfivLC0NoeiXCbVuz9MvnkEv58uEMEmRv1Jj2DDofPPfL%3D5mA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
