I am pretty sure that our Release Automation infra would not mind to cut a release on Dec 30, but there is still a lot of manual work involved in cutting an LTS release. I am +1 for postponing, especially if there are no major issues to be addressed.
Postponing the release would also give more time for ramp-up to a new release officer whose term starts on Dec 03. Best regards, Oleg On Wednesday, November 11, 2020 at 7:32:53 PM UTC+1 [email protected] wrote: > +1 > > On Nov 11, 2020, at 1:54 AM, [email protected] <[email protected]> > wrote: > > +1 > > On Wednesday, November 11, 2020 at 10:42:01 AM UTC+1 [email protected] > wrote: > >> +1 >> >> On Wednesday, November 11, 2020 at 10:15:24 AM UTC+1 Raul Arabaolaza >> wrote: >> >>> +1 >>> >>> On Wednesday, November 11, 2020 at 10:08:45 AM UTC+1 Ildefonso Montero >>> wrote: >>> >>>> +1 >>>> >>>> On Wednesday, November 11, 2020 at 10:01:20 AM UTC+1 Antonio Muñiz >>>> wrote: >>>> >>>>> +1 >>>>> >>>>> On Wed, 11 Nov 2020 at 09:48, Daniel Beck <[email protected]> wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> We have an LTS release scheduled for December 30, which probably >>>>>> isn't useful: The RC testing period is from Dec 16 to Dec 30. Plus who >>>>>> wants to release things the day before NYE? >>>>>> >>>>>> I propose we add a two-week break between 2.263.1 release and 2.263.2 >>>>>> RC, postponing all future RCs and releases by two weeks accordingly. >>>>>> >>>>>> Before: >>>>>> Dec 2 - 2.263.1 Release >>>>>> Dec 16 - 2.263.2 RC >>>>>> Dec 30 - 2.263.2 Release >>>>>> etc. >>>>>> >>>>>> After: >>>>>> Dec 2 - 2.263.1 Release >>>>>> Dec 30 - 2.263.2 RC >>>>>> Jan 13 - 2.263.2 Release >>>>>> etc. >>>>>> >>>>>> This should give us a useful RC testing period in early January. >>>>>> Since this is the .2 release, a slightly longer backporting period in >>>>>> December could help getting more fixes in for issues discovered in .1 as >>>>>> well. >>>>>> >>>>>> While the RC would be scheduled for Dec 30, it could always be >>>>>> prepared earlier if nobody would be around in late December to do it. If >>>>>> that doesn't work out and it is published in early Jan, that wouldn't be >>>>>> too much of a delay either. >>>>>> >>>>>> WDYT? >>>>>> >>>>>> Daniel >>>>>> >>>>>> -- >>>>>> 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/821EFEC7-55BA-475B-B977-1DCC1F559B82%40beckweb.net >>>>>> . >>>>>> >>>>> >>>>> >>>>> -- >>>>> Antonio Muñiz >>>>> Human, Engineer >>>>> CloudBees, Inc. >>>>> >>>> > -- > 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/46de2d26-f36e-422a-820c-03cf70343416n%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/46de2d26-f36e-422a-820c-03cf70343416n%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/4388d9bd-09dd-4dba-9391-d3ef99dbfe45n%40googlegroups.com.
