@Mark Waite <mark.earl.wa...@gmail.com> to be clear were you asking for an RC delay as well or just the final release date?
On Fri, 13 May 2022 at 15:02, Tim Jacomb <timjaco...@gmail.com> wrote: > Thanks! Go for it > > On Fri, 13 May 2022 at 14:52, Alexander Brandes <mc.cach...@gmail.com> > wrote: > >> Heyo all, >> >> I'd like to take care of it, if possible. >> >> ~Alex >> >> On Friday, 13 May 2022 at 00:06:02 UTC+2 timja...@gmail.com wrote: >> >>> Sure, I've moved the release date 2 weeks out. >>> >>> New dates: >>> RC: 18th May >>> Release day: 15th June >>> >>> On Tue, 10 May 2022 at 17:51, Mark Waite <mark.ea...@gmail.com> wrote: >>> >>>> >>>> >>>> On Tue, May 10, 2022 at 9:23 AM Tim Jacomb wrote: >>>> >>>>> Hello >>>>> >>>>> Is anyone interested in being the release lead for 2.346.1? >>>>> >>>>> Planned dates can be seen on the event calendar: >>>>> https://www.jenkins.io/events/#event-calendar >>>>> Release candidate by 18th May >>>>> Release on 1st June >>>>> >>>>> >>>> Would you be willing to consider a 2 week delay in that final release >>>> date, so that it would be June 15 rather than June 1? >>>> >>>> The original scheduled date to select the LTS baseline was April 20, >>>> 2022. We delayed that by a little less than 3 weeks so that we could >>>> assure that the selected LTS baseline had fewer open issues and good >>>> ratings. We've had great results from that effort, but I still feel that >>>> we need three weeks to watch for issues in the selected baseline (2.346), >>>> then two weeks to test the release candidate. That's removing one week >>>> from our usual pattern of four weeks from baseline selection to release >>>> candidate then two weeks from release candidate to release. >>>> >>>> I acknowledge that the final decision on release date is best decided >>>> by you as the release officer. I'm lobbying for the delay of the release >>>> date but fully accept that the decision is yours to make, not mine. Thanks >>>> for being the Jenkins release officer and thanks so much for your >>>> contributions to Jenkins. >>>> >>>> Mark Waite >>>> >>>> >>>> -- >>>> 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-de...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHfBQVdgbdWPbYZWsEMxq%3DUO%2BF4eHW5EvCcsDRgYBextg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHfBQVdgbdWPbYZWsEMxq%3DUO%2BF4eHW5EvCcsDRgYBextg%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/12b049d5-1811-4da4-a59b-f468df396ac3n%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/12b049d5-1811-4da4-a59b-f468df396ac3n%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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif9HqM1JzmfDUwyP3q8tZV-gxyfxL%3DMCcuML4REws7%2Bzw%40mail.gmail.com.
