 Welcome everyone. This is the 1st of June 2023. It's Jenkins documentation office hours topics for today. 2.401.1 has released the internationalization pull request has merged and end of life notifications and then main newsletter. Any other topics Bruno that you want to include on the list. No, thank you, Mark. I don't have any. Okay, so delighted that 2.401.1 has released. And looking positive let's take a quick look at the ratings on the page just to see. So if we look at the download page and see what the current ratings are. We've got 3030 positives and no negatives and I've been using it happily so I'll increment by one. Good. Right. So it looks it looks promising. That's that's good. Now we're only one day into it. Yeah, but that's a good, good sign. The internationalization pull request from Jay Chen has been merged. He approved he or she, the person approved the changes I had proposed and has submitted a new pull request. So the new request free. All right, Jeffrey, so probably mail. Right. Yes. So here's the new pull request. I won't get to this one for a while. I suspect it requires the same kinds of changes structural and organizational adjustments as the earlier one did. There are things that were in the old wiki that have a place in the new in the new site in the current site, but not exactly a direct translation. Right. There's there are better ways to approach it. So. So I've done the first review but just on the syntax. It won't help that much. But yes, now. Oh, it's work for the grown ups. Well, thank you for doing that. That's great. Oh, and they did it again off their master branch. Okay. Yeah. Thank you for the reminder for them. We we it. It's not a terrible inconvenience, but it just complicates my life as a reviewer when someone uses the master branch instead of on their own copy instead of using using a feature branch or a separately named branch. But to be totally honest, it's not that clear in the documentation I linked in my comment. Oh, good. Okay, so we should make it more clear. Yes, it's written something like to a branch but not to a new branch that is not made no master. So I should do that. Great. Very good. All right, thank you. Anything else on the internationalization pull requests. No, thank you. Okay, next topic was end of life notifications in Jenkins core and here we've gone one step further now. We have a blog post. It announces it. And one of the one of the mistakes I've made that needs to be corrected is that the redirect from the page inside Jenkins needs to go to the blog post. So today, inside Jenkins there's a hyperlink refer to this documentation for details. When the person clicks on that hyperlink, it will take them to the Jenkins Linux requirements page, which is not bad, but I think it would be clearer for them if it took them to the blog post. Yes, indeed. So this is not a bad pay or no wrong one that it takes into the Linux support policy. This is not a bad page. The blog post at least for the next several weeks or a month is probably a more accurate expression of exactly what's happening and why it's happening. Got it. So that's that's a to do item for somebody. Do you have you ever created a redirect brutal. No. I was just wondering, of course, you have some old system running that will display that information. I don't run any old OS, so I won't see that. Correct. So what you'd have to do is, you're correct. The only users who will see this are users who are running an operating system that will either has already reached end of life, or will reach end of life within the next six months. Or in the case of Red Hat Enterprise Linux and its derivatives. We show that to them if you're using Red Hat Enterprise Linux seven immediately, even though the operating system provider end of life is June 30. We're going to end life for it in the Jenkins project November 16. Yeah, so now. I was just, I was going to see, hey, Bruno, do you want to try to update the existing redirect. Yeah, but they're willing to do it. Try to update the redirect to point to the blog post. Oh, it's in Jenkins core code. No, no, this is actually not a change in Jenkins core at all. That's the nice thing about this redirect. We direct redirect. So if we were to look inside the poll request, we can find the URL. Okay. So let's go looking there. And we'll find it. So core. We look at poll requests, and we say warn. Come on. And look at closed. And here it is. Okay, so here. Now inside the source code of this poll request and the files changed, refined a reference to www.jankins.io. This reference right here. That is the, that is the redirect. And so. Oh, so it's directly in Jenkins.io repo and not in Jenkins core. Okay. Right. And, and what you'll do is you'll find that on the Jenkins.io source code. If you do a search for it. Oh, no, I searched badly. If we do a search for this. I think it will find it for us. Yeah, there it is. And so this is the file that needs to be changed. Okay. Oh, okay. So it's not a guidance into a complete tutorial. Thanks a lot for writing. Well, and my apologies, it's just, I want to be sure you have a chance of success. So yeah, that's kind of that. That file needs to change. And what it needs to change to is point to the blog post, instead of the Linux requirements page. Okay, thanks a lot Mark. This is a recipe for success. Right. Okay, great. Then then the next topic we had was the main newsletter and their Marko submissions. I'll hopefully get to those late today. Because now that we're past the end of the month, I can say you with confidence which things happen at which to go. Yeah. All right. Any other topics Bruno. No, thank you, Mark. Okay, let's call an end for today and see everybody in 20 minutes at the live stream on what's new in Jenkins 2.401.1.