LTS schedule winter break

[Daniel Beck]

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

[Antonio Muñiz]

+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 jenkinsci-de...@googlegroups.com.
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.

[Ildefonso Montero]

+1

[Raul Arabaolaza]

+1

[bmu...@cloudbees.com]

+1

[fque...@cloudbees.com]

+1

[Marky Jackson]

+1

> On Nov 11, 2020, at 12:48 AM, Daniel Beck <m...@beckweb.net> wrote:
>
> Hi everyone,

[Baptiste Mathus]

+1, makes sense especially to preserve the lives of the people involved.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/F17409E1-8728-48F5-9DDF-76ADFA8CD3A6%40gmail.com.

[Mark Waite]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5%3DYZZTpfK6RkJite1AVsipreddXrqYqR-sLyq1e6eKVQ%40mail.gmail.com.

[Tim Jacomb]

Is someone going to want to do an RC on 'Dec 30 - 2.263.2 RC' though?

could we leave the RC date as the 16th and then release it on the 13th?

(creating more RCs as needed if required)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHzjHHM-dY%3D5ciyn%2BiY4C8sz7a3KsrothmNN%3DLWh4xnKQ%40mail.gmail.com.

[Daniel Beck]

On Wed, Nov 11, 2020 at 3:01 PM Tim Jacomb <timja...@gmail.com> wrote:

Is someone going to want to do an RC on 'Dec 30 - 2.263.2 RC' though?

I address that in my proposal, that can always be created earlier if necessary due to scheduling/vacation issues. If you implement it as you propose, there will still be an RC on the 30th, just two weeks old. No matter when the actual RC is created, it's probably a good idea to do backporting and backporting review fairly early in any case.

[Vlad Silverman]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46de2d26-f36e-422a-820c-03cf70343416n%40googlegroups.com.

[Oleg Nenashev]

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

[Tim Jacomb]

Well RC builds aren’t automated yet...

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4388d9bd-09dd-4dba-9391-d3ef99dbfe45n%40googlegroups.com.

[Victor Martinez]

+1

Just a quick question regarding the winter break, even if the release dates are not known yet I wonder whether the calendar could be potentially changed to reflect a potentially release freeze for the last two weeks of the year and the new week of next year by default? This is something that have been happening for the last years as de facto standard,.

Cheers 

[Oliver Gondža]

Hey, Thank you all for the inputs. I approve the suggested timeline, so
the calendar is updated.

Please do not count on the exact RC date in late December.

On 12/11/2020 00.43, Victor Martinez wrote:
> +1
>
> Just a quick question regarding the winter break, even if the release
> dates are not known yet I wonder whether the calendar could be
> potentially changed to reflect a potentially release freeze for the last
> two weeks of the year and the new week of next year by default? This is
> something that have been happening for the last years as de facto standard,.
>
> Cheers
>
> On Wednesday, 11 November 2020 at 20:41:37 UTC Oleg Nenashev wrote:
>
> 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
> vsilv...@gmail.com wrote:
>
> +1
>
>> On Nov 11, 2020, at 1:54 AM, fque...@cloudbees.com

>> <http://cloudbees.com> <fque...@cloudbees.com> wrote:
>>
>> +1
>>
>> On Wednesday, November 11, 2020 at 10:42:01 AM UTC+1

>> <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 jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-de...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-dev/bce5c807-773a-483d-a501-36d10f9628c1n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/bce5c807-773a-483d-a501-36d10f9628c1n%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
oliver