 So welcome to Jenkins Platform Special Interest Group. It's the 11th of February, 2022. Topics we've got on the agenda include open action items, require Java 11 or newer, Linux operating system support policy, switching Linux packages from System 5 in it to System D, and an exit lifecycle change. Sahitya, any other topics you'd like to put on the agenda? No, sir. Okay, great. Well, thank you for joining. So I'm just going to go through these. I think the meeting will be relatively brief. So we've still got the open action item on plugin installation manager documentation. That's one that I need to take action on. It's just lower priority given other things are much more pressing. The most interesting one for today's session is that we're laying out plans for when we will make the transition to no longer use Java 8 as a working choice for the Java version used by Jenkins. And so this Jenkins enhancement proposal that is on screen right now is proposing what the steps are we should take in order to switch from Java 8 to Java 11 as the primary JVM. So let's get that visible. And it talks about the plan. It talks about which changes need to be made, why, et cetera. So, so encourage people to review it. Welcome them to review it, et cetera. Okay. There are, there is an Epic in Jira that is tracking this. And it's got four or five items right now. There are a number of candidate issues that need to be reviewed. And there are, there's the Java 11 Epic whose its issues also need to be reviewed. So there are a number of places where we can use help as people look at this to see are there other problems that we may confront as we drop support for Java 8 and make Java 11 our new minimum. Yes, sir. Then the next that any questions on the Java 11 change. I am new to this open source organization. So I want to know how I will, you know, contribute the course. Oh, good. And I am happy to help you with that. That you with that, Sahitya, let's, let's plan a time when we could do some, some, some mentoring and you could join us for Google summer of code office hours, for instance, or documentation office hours and happy to give you help getting started there. Definitely. Great. So if you want to just ping me separately as Mark dot Earl dot wait at Gmail dot com on email, I'll be happy to schedule a time with you to help you get started. Yeah, yes, sir. Yes. All right, thank you. So then on Linux operating system support policy, we've not had an explicitly declared support policy in the past. So this document is adding an official support policy. And it talks about why we want this policy, what the platforms are that will support, etc. This was opened about a month ago and recently was revised. Look forward to people doing further review of it before we before we merge it. Okay. The last topic is on the Linux installer packages so the RPM for red hat the RPM for Susie and the Debian package are currently using system five in it as their as their initialization manager. We're going to switch that to the more modern system D as part of a poll request that's been submitted by Basel Crow. That poll request needs much more testing. It needs more documentation. So if you'd like to contribute to Jenkins this is actually it might be an interesting place to help us with performing tests and exploring it. Yeah, if you refer to this poll request here, you can see some guidelines on how to test it, the kinds of things to be tested, some of the bugs that are being fixed by it, etc. We'd love to have your help there if you've got Linux experience. Yeah, or if you're interested in developing having Linux experience. Yes, this is sure. Great. All right, thank you. And then we've got a some changes that are have recently merged to Jenkins core that first became available in Jenkins to dot three hundred thirty three. That will first be visible in a long term support release in June of twenty twenty two. So this change won't be fully implemented until at least June of twenty twenty two based on current plans. Yeah, those are the topics that we wanted to cover today. Any other topics. Other than you and I scheduling a separate session for some, some onboarding. Sir, I want just to know how to contribute. Just that's the main topic. Great. And I am happy to help you with that. We'll, we'll, if we can do that in a separate session, just send me an email message and we'll do some planning for that. Yeah. All right. Thank you. Then I'm going to go ahead and call this meeting done. And thanks very, very much. And we'll meet again in two weeks. Definitely.