Add Jeremie Playout as a Jenkins LTS release lead

[MarkEWaite]

GitHub repositories

@jplayout needs to be added to the

• @jenkins-infra/release and
• @jenkinsci/release teams

GitHub users to have permission

@jplayout

Permission level

Write

Justification

@jplayout has volunteered to be the Jenkins 2.492.1 release lead. The first release candidate of that release will be 22 Jan 2025.

Per the access permissions described in the Jenkins LTS release process, @jplayout needs to be added to the @jenkins-infra/release team and the @jenkinsci/release team so that he has access to create the LTS release checklist for Jenkins 2.492.1. Membership in those teams will allow him to be the 2.492.1 release lead and run the steps for that newly created checklist.

While adding him to the @jenkins-infra/release team, it would be good to add @krisstern as well. Kris has been the Jenkins LTS release lead multiple times without being added to that team, so I assume that permissions were granted some other way.

[timja]

While adding him to the @jenkins-infra/release team, it would be good to add @krisstern as well. Kris has been the Jenkins LTS release lead multiple times without being added to that team, so I assume that permissions were granted some other way.

I don't think Kris had permissions on the jenkins-infra repository someone else probably just merges the PRs (likely me).

Generally we wouldn't add people on their first release but in this case I think should be ok.

I've added Kris to the jenkins-infra release team.

[krisstern]

Thanks @MarkEWaite and @timja! Appreciate it

[MarkEWaite]

I've added @jplayout to the repository security settings of the release repository. That gives him the same permissions as @cathychan , @imonteroperez , and @res0nance and should be enough for him to be the 2.492.1 release lead. I think that it is better to eventually add all those users to the @jenkins-infra/release team rather than maintain them as users added separately to the repository security settings, but his current permissions in that repository should be enough for him to act as release lead.

I pushed the initial 2.492.1 commit and the stable-2.492 branch from @jplayout to Jenkins core. Now that the stable-2.492 branch exists, I think that @jplayout has enough permissions to complete the 2.492.1 release, since core maintainers will review and merge any backporting pull requests.

The 2.492.1 LTS release checklist is now in progress. Release candidate is scheduled for Wednesday 22 Jan 2025.