On Thu, Jun 23, 2022 at 7:54 PM Olivier Lamy <[email protected]> wrote: > Personally (and conservative POV) I do not feel a rush to push release this > and include it ASAP in weekly. > but cool kids may have different opinions about doing it ASAP :) well do it. > As weekly already has big changes coming with java 11. > Probably not many issues but better to not have collisions with possible > issues coming with a Jetty upgrade as well.
I could see arguments for both sides. On the one hand, the content of the September LTS is heavily focused on platform improvements, and this fits with that theme. On the other hand, it is an orthogonal change, as you note, and it may be tough to differentiate the cause of an issue when it could be due to either the Java 11 upgrade or the Jetty upgrade. I actually had a similar concern with Guava and Guice (and with Ant changes prior to that), so I employed a strategy of staggering changes across multiple weeklies. That way, if a user encounters a problem, we can ask them to roll back to an intermediate weekly and thereby bisect more easily. So I think this concern could be alleviated by waiting a week or two after the Java 11 weekly lands before we have a Jetty 10 weekly. The staggering effect should hopefully make it easier to support users via bisection. And I think waiting a week or two still gives us plenty of soak time before LTS. In fact, it may even take us about that long to test the Jetty 10 PR with PCT/ATH anyway. (BTW, this isn't the only change I am planning to stagger in this way. I am also holding off on JUnit 5 for the same reason: trying to stagger risky changes across multiple weeklies for ease of bisection.) > Maybe incremental build could be tested with all the chain ath, pct etc... I concur. PCT/ATH is clearly appropriate. > I will be off until next weekend so if you need changes feel free to push > them in the branch. It's supposed to be a community branch to share the work. You have definitely done the lion's share of the work in that branch, for which I am exceedingly grateful. I did not realize you were OK with others pushing to a communal branch, but I am delighted that you are! I love working this way, and perhaps we can use that as a pattern for collaboration going forward. I just pushed two more commits to the branch, and we now have a green PR build! We should be able to start testing that build with the core test suite and PCT/ATH after the next weekly release. If nobody volunteers to do it I will try and run some tests after I finish dealing with the Java 11 tasks. > I will be off until next weekend > Cheers and enjoy your weekend, I hope you enjoy the weekend as well, Olivier. I look forward to finishing this up together with you when you return, if it isn't finished already! As you wrote many times, this is all about coming together as a community, and I am excited we are so close to the finish line. -- 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/CAFwNDjqMH0xePem0Mh0sGVDs1tUiNW1Yq_o%2B9iWYkSDYsfsKtg%40mail.gmail.com.
