Re: Backporting for LTS 2.401.2 has started

[Kris Stern]

Sure @Basil Crow<mailto:m...@basilcrow.com> please go ahead with a backporting 
PR, and ping me there as well.

Best,
Kris

From: jenkinsci-dev@googlegroups.com  on behalf 
of Alexander Brandes 
Sent: 10 June 2023 01:26
To: Jenkins Developers 
Subject: Re: Backporting for LTS 2.401.2 has started

+1 for the monitor, works well on my CentOS 7 instance.

On Friday, 9 June 2023 at 19:11:26 UTC+2 timja...@gmail.com wrote:
+1 for EOL Monitor

On Fri, 9 Jun 2023 at 18:01, Basil Crow  wrote:
That makes sense to me, and I think an exception is justified for
time-sensitive areas, such as EOL notifications. The feature has been
in weeklies without any reports of regression.

On Fri, Jun 9, 2023 at 8:34 AM Mark Waite  wrote:
> I would like to inform users earlier about end of life operating systems, if 
> that difference from the standard LTS backporting rules would be allowed.
>
> Specifically, we would backport:
>
> Warn when operating system end of life is approaching - 
> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
> Fix Fedora 38 date in operating system end of life warning - 
> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
>
> That would make the operating system end of life warning visible to LTS users 
> 8 weeks before it would naturally become visible.
>
> This is backporting a feature, so I am also just fine if this is rejected, 
> since it is not according to the standard backporting rules where we rarely 
> backport features to an LTS line.
>
> I would revise the blog post that announces the end of life operating system 
> warning to state that the warning is available to LTS users in 2.401.2
>
> 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/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%40mail.gmail.com.

--
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<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/06503203-56eb-4466-8534-5c7d5324181bn%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-dev/06503203-56eb-4466-8534-5c7d5324181bn%40googlegroups.com?utm_medium=email_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/OS3P286MB1431C0BE608F0B4F200D17BAA156A%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.COM.

Re: Backporting for LTS 2.401.2 has started

[Alexander Brandes]

+1 for the monitor, works well on my CentOS 7 instance.

On Friday, 9 June 2023 at 19:11:26 UTC+2 timja...@gmail.com wrote:

> +1 for EOL Monitor
>
> On Fri, 9 Jun 2023 at 18:01, Basil Crow  wrote:
>
>> That makes sense to me, and I think an exception is justified for
>> time-sensitive areas, such as EOL notifications. The feature has been
>> in weeklies without any reports of regression.
>>
>> On Fri, Jun 9, 2023 at 8:34 AM Mark Waite  wrote:
>> > I would like to inform users earlier about end of life operating 
>> systems, if that difference from the standard LTS backporting rules would 
>> be allowed.
>> >
>> > Specifically, we would backport:
>> >
>> > Warn when operating system end of life is approaching - 
>> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
>> > Fix Fedora 38 date in operating system end of life warning - 
>> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
>> >
>> > That would make the operating system end of life warning visible to LTS 
>> users 8 weeks before it would naturally become visible.
>> >
>> > This is backporting a feature, so I am also just fine if this is 
>> rejected, since it is not according to the standard backporting rules where 
>> we rarely backport features to an LTS line.
>> >
>> > I would revise the blog post that announces the end of life operating 
>> system warning to state that the warning is available to LTS users in 
>> 2.401.2
>> >
>> > 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/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%40mail.gmail.com
>> .
>>
>

-- 
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/06503203-56eb-4466-8534-5c7d5324181bn%40googlegroups.com.

Re: Backporting for LTS 2.401.2 has started

[Tim Jacomb]

+1 for EOL Monitor

On Fri, 9 Jun 2023 at 18:01, Basil Crow  wrote:

> That makes sense to me, and I think an exception is justified for
> time-sensitive areas, such as EOL notifications. The feature has been
> in weeklies without any reports of regression.
>
> On Fri, Jun 9, 2023 at 8:34 AM Mark Waite 
> wrote:
> > I would like to inform users earlier about end of life operating
> systems, if that difference from the standard LTS backporting rules would
> be allowed.
> >
> > Specifically, we would backport:
> >
> > Warn when operating system end of life is approaching -
> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
> > Fix Fedora 38 date in operating system end of life warning -
> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
> >
> > That would make the operating system end of life warning visible to LTS
> users 8 weeks before it would naturally become visible.
> >
> > This is backporting a feature, so I am also just fine if this is
> rejected, since it is not according to the standard backporting rules where
> we rarely backport features to an LTS line.
> >
> > I would revise the blog post that announces the end of life operating
> system warning to state that the warning is available to LTS users in
> 2.401.2
> >
> > 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%40mail.gmail.com
> .
>

-- 
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-3BicNBhkfeD6pq0OeR4fZQQEYUkvCYbbbtA7MMGTgWCUnng%40mail.gmail.com.

Re: Backporting for LTS 2.401.2 has started

[Basil Crow]

That makes sense to me, and I think an exception is justified for
time-sensitive areas, such as EOL notifications. The feature has been
in weeklies without any reports of regression.

On Fri, Jun 9, 2023 at 8:34 AM Mark Waite  wrote:
> I would like to inform users earlier about end of life operating systems, if 
> that difference from the standard LTS backporting rules would be allowed.
>
> Specifically, we would backport:
>
> Warn when operating system end of life is approaching - 
> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
> Fix Fedora 38 date in operating system end of life warning - 
> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
>
> That would make the operating system end of life warning visible to LTS users 
> 8 weeks before it would naturally become visible.
>
> This is backporting a feature, so I am also just fine if this is rejected, 
> since it is not according to the standard backporting rules where we rarely 
> backport features to an LTS line.
>
> I would revise the blog post that announces the end of life operating system 
> warning to state that the warning is available to LTS users in 2.401.2
>
> 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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%40mail.gmail.com.

Re: Backporting for LTS 2.401.2 has started

[Mark Waite]

On Sunday, June 4, 2023 at 12:33:51 PM UTC-6 Kris Stern wrote:

Hi Alex,

Actually yes, the selected issues are blank right now as there has been no 
issue tagged with the "lts-candidate" label yet. Let me go through all 
suitable candidates and add this label soon. Meanwhile, if any issue is 
recommended to be included in this release, please do let me know. 

Cheers,
Kris


I would like to inform users earlier about end of life operating systems, 
if that difference from the standard LTS backporting rules would be allowed.

Specifically, we would backport:

   - Warn when operating system end of life is approaching 
   - https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
   - Fix Fedora 38 date in operating system end of life warning 
   - https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)

That would make the operating system end of life warning visible to LTS 
users 8 weeks before it would naturally become visible.

This is backporting a feature, so I am also just fine if this is rejected, 
since it is not according to the standard backporting rules where we rarely 
backport features to an LTS line.

I would revise the blog post 
 that 
announces the end of life operating system warning to state that the 
warning is available to LTS users in 2.401.2

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/965e8267-9f34-4a14-8d8a-ff4fabd0eef9n%40googlegroups.com.

Re: Backporting for LTS 2.401.2 has started

[Mark Waite]

On Friday, June 9, 2023 at 9:17:40 AM UTC-6 Basil Crow wrote:

As others have noted, there is not really anything to backport at the
moment. How do others feel about backporting #7990 and #8065?

Context: Without dropping support for javax.inject, these changes add
support for jakarta.inject annotations, allowing a migration to begin
once plugins select a baseline that includes these changes.

The changes have shipped in a weekly without any issues. From my
perspective the backport is low-risk and would allow us to begin the
jakarta.inject migration sooner throughout the rest of the plugin
ecosystem rather than waiting for the next LTS line.

On the other hand, this does go against our usual policy of not
backporting changes with API surface area, so I do not feel strongly
about this backport either way.

If acceptable, I would be happy to create the backport PR.


I am +1 for that backport.  I think it makes sense to begin that migration 
sooner. 

-- 
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/c373b38d-e31c-4fd9-af83-674c7791abe6n%40googlegroups.com.

Re: Backporting for LTS 2.401.2 has started

[m...@basilcrow.com]

As others have noted, there is not really anything to backport at the
moment. How do others feel about backporting #7990 and #8065?

Context: Without dropping support for javax.inject, these changes add
support for jakarta.inject annotations, allowing a migration to begin
once plugins select a baseline that includes these changes.

The changes have shipped in a weekly without any issues. From my
perspective the backport is low-risk and would allow us to begin the
jakarta.inject migration sooner throughout the rest of the plugin
ecosystem rather than waiting for the next LTS line.

On the other hand, this does go against our usual policy of not
backporting changes with API surface area, so I do not feel strongly
about this backport either way.

If acceptable, I would be happy to create the backport PR.

-- 
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/39d42ac6-5d09-4d92-85da-e559a0aa85f1n%40googlegroups.com.

Re: Backporting for LTS 2.401.2 has started

[Kris Stern]

Hi Alex,

Actually yes, the selected issues are blank right now as there has been no 
issue tagged with the "lts-candidate" label yet. Let me go through all suitable 
candidates and add this label soon. Meanwhile, if any issue is recommended to 
be included in this release, please do let me know.

Cheers,
Kris

From: jenkinsci-dev@googlegroups.com  on behalf 
of Alexander Brandes 
Sent: 04 June 2023 16:02
To: Jenkins Developers 
Subject: Re: Backporting for LTS 2.401.2 has started

It appears you forgot to select issues you want to backport. The query is empty.

On Saturday, 3 June 2023 at 05:20:02 UTC+2 kris...@outlook.com wrote:
Hi everyone,


Backporting for 2.401.2 has started, and the RC is scheduled for Wednesday, 
June 14th, 2023.


Candidates: https://issues.jenkins.io/issues/?filter=12146

Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-fixed
Rejected: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-rejected


Best,

Kris


--
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<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b69ac7b9-ca5c-4f3d-ba0e-5cc3496aabd1n%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-dev/b69ac7b9-ca5c-4f3d-ba0e-5cc3496aabd1n%40googlegroups.com?utm_medium=email_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/OS3P286MB1431A471E04F356565EACB88A14CA%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.COM.

Re: Backporting for LTS 2.401.2 has started

[Alexander Brandes]

It appears you forgot to select issues you want to backport. The query is 
empty.

On Saturday, 3 June 2023 at 05:20:02 UTC+2 kris...@outlook.com wrote:

> Hi everyone,
>
> Backporting for 2.401.2 has started, and the RC is scheduled for 
> Wednesday, June 14th, 2023.
>
>
> Candidates: https://issues.jenkins.io/issues/?filter=12146
> Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-fixed
> Rejected: 
> https://issues.jenkins.io/issues/?jql=labels%20%3D%202.401.2-rejected
>
> Best,
>
> Kris
>
>
>

-- 
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/b69ac7b9-ca5c-4f3d-ba0e-5cc3496aabd1n%40googlegroups.com.