Hey Wadeck, thanks for the clarification from the views of the security team, that sounds reasonable. I'd want to go ahead and merge the PR later today, considering nobody expressed blocking reviews in over a week.
To 1), that's a call Tim has to agree to as well. But like you already stated, delaying them might not be the best solution, however, I have no strong objections about it, if the security team needs a bit more time in advance. ~ Alex On Tuesday, 7 June 2022 at 18:20:52 UTC+2 [email protected] wrote: > Hey there, especially Alex, > > Usually we have a two weeks period for the RC, once the backports are > merged. In this case, we have a PR that is still pending, ~one week after > the expected delay. > PR in question: https://github.com/jenkinsci/jenkins/pull/6618 > > So, two questions: > 1) Is it OK if we are *postponing the release by one additional week*? a) > to have two weeks of test for the RC, b) to get more time for the security > release that requires to have that PR merged. It would mean that the LTS > will be released on June 22. (and thus the Java 11 should be postponed > again) > 2) When do you plan to merge the PR? > > The second wave of backports seems to contain important fixes, so > postponing those seems to be not really an option. > > Best regards, > > Wadeck > On Tuesday, May 31, 2022 at 8:37:24 PM UTC+2 [email protected] wrote: > >> On Fri, May 27, 2022 at 3:03 AM Alexander Brandes <[email protected]> >> wrote: >> > >> > If there are no objections against it, I'd like to use the additional >> time and start a secondary backporting process from past weekly releases to >> integrate the new LTS candidates. >> >> +1 >> > -- 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/5c711ab6-94ba-446d-bf30-e1659fa82368n%40googlegroups.com.
