Not answering on the revert or change of James' fix itself, but FWIW we at CloudBees plan to start deeper testing on the newer baseline, especially >= 2.199 very soon, hopefully in the next few days. Hopefully this will provide an additional data point as to the size of the potential impact of this Core change.
On Thu, Nov 21, 2019 at 11:38 AM James Nord <[email protected]> wrote: > I will state this again -* no level of dataloss is acceptable* - we > should not back this change out or make it disabled by default. > > There is a drive by untested PR to Configuration As Code plugin if someone > wants to look at it. > > https://github.com/jenkinsci/configuration-as-code-plugin/pull/1204 > > /James > > On Thursday, November 21, 2019 at 7:51:39 AM UTC, ogondza wrote: >> >> I like that idea, Jesse. Can we agree on picking 2.204 with JENKINS-58993 >> patched to only fail when assertions are on? >> >> -- >> oliver >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/3588ff14-54bc-4d6e-99c8-1144bc502683%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/3588ff14-54bc-4d6e-99c8-1144bc502683%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp0Yd-zHe%3DBu%3DCMHhcv5DhHj023qp5n5i3nZVPGh0JStmg%40mail.gmail.com.
