 Welcome, it's documentation office hours. This is the 26th of May 2023 topics for today, the 2.401.1 change log and upgrade guide. Internationalization and localization a new poll request and some opportunities to review there. If Chris joins us we can talk about Google summer of code and we'll talk about end of life notifications in Jenkins core. Any other topics you want to put on the list Meg. Looks good to me. All right, so let's take a first look at topic number one the 2.401.1 change log with Kevin out of the office. I've created it. And so here's what it looks like. If you've got capacity Meg, I'd love to have you review if you don't don't worry about it. Nope happy to do it. This is one of those that these things are phrased a very specific way Daniel Beck has guided us on how to do those and so comments are welcomed and happily encouraged. Okay. So what what this will then do is next Wednesday when the LTS releases this will be available and merged and that's what will show up on the change log here and on the upgrade guide here. Okay. So Bruno will also review it and I suspect Alex Brandis will review it so we've got good review there. Next topic then was on internationalization and localization so this one. We've got a poll request from from Jeffrey Chen, a new contributor. The poll request is bringing back an old poll request that had been started and then stalled. So we had started a stalled and Jeffrey said hey I'd like to work on it. So started work on it and Jeffrey's work is now visible here and we've been going through a series of improvements to try to get it ready right now it's running through the build what I had done was Jeffrey gave some initial changes that looked like this. So here you see the top level page notice that it's still marked with the work in progress flag. He added a whole new page, or rather the original poll request did. And then the top level page still showed as work in progress with a link to the new page. I took a little broader approach and said hey let's do it this this other way. And so what I did was put the content that he created in the top level page. There's a series of hey do this do this links to how to guides, and then place the integration to crowd in right next to it, and linked inside because crowd in is this great tool that we use for to support our translators. Right. So I asked Jeffrey hey are you okay if I apply my changes on to your poll request. Jeffrey's answer back seems to be yes. And so I've gone ahead and done that. And it's now building I just pushed it just a few minutes ago. So we'll be able to see that. And this is another one may God love to have a review, particularly because we want to, we'd like to have this done well enough that people can understand it there are two or three cases where translators can do the easy thing. If their plug if the plug in they're working on is supported by crowd and they just have to do this translate messages and crowd in right and it talks them how to do that it's it's a really nice interface. If it's not supported in crowd in the easiest thing is ask the maintainer please put it into crowd in. But if they don't do that, then there are these steps that describe okay here's how you do it the hard way. Do you see the type of a number one. I do and I fixed it and it'll be in the next generated. Okay. Yes, thank you. That's the sort of thing one misses the I just what exactly you look at them too much. So, so this is, this is what what the concept here is that this is wandering between how to guides. These three here, and the reference guide, the so the reference book has links that take people back and forth depending on which I think made most sense. And so so we we hope that they will find this useful it's and the content is much fuller now there's much more content now. So if if you're available to review it. Absolutely. And for me there the additions are at least good enough for us to consider are we ready are we good enough to merge. Okay, I will look at that either tonight or tomorrow. Great, thank you. Alright, on Google summer of code since Chris isn't here we'll move this later. Next topic was end of life notifications in Jenkins core so this one is a process that I had started discussing in platform see again in Docs office hours. To warn users when their operating system is no longer supported because we don't support operating systems that the vendor doesn't support. And so this now gives us a user interface inside Jenkins that says, you're running on an operating system we won't be supporting in the not too distant future. This, the example we see here is specifically sento seven, and I've proposed that we will accelerate its end of life it would officially end life, June of 2024. We're going to end life in the Jenkins project in November of 2023, because this thing is an albatross around our necks. Oh, God, what a hard system that was. Well, it's, it's impressive how long lived it is. It is very impressive. Yeah. And so, so the, the message here is takes them through it. Now we've got a number of activities that have to be done. And I've put some notes in here on those will need a blog post. And just to go with the blog post will want to community dot Jenkins that I oh post that tells people so that people can have conversations about the blog post. The other thing is this gives us an a dedicated operating system redirect page, or it gives us a link to an operating system page. But right now that link is just going to a generic Linux support page. Okay. I think what we want to do is I'm going to show it to you and I think we want to switch this generic this general purpose page to be specific. So I'm going to follow that hyperlink. Notice that all it did is it redirected to the Linux support policy and I suspect we want a dedicated page for this that says, Hey, and maybe it's just a link to the blog post initially. Yeah. What do you think what what would you recommend what will actually I am a pretty a free question. What does supported mean here. It does not mean the support there is no support organization. Correct. It does not. So in this case, it doesn't run we don't test against it. Right. So the, the, the simplest way of describing supported is if we if we run automated tests against it. And are committed to maintaining it running on that we call it level one. Okay. And we enumerate them specifically here. Okay, 64 bit Linux on Debian on red hat on open Susie 64 bit Linux and those are the AMD 64 when 64 bit Linux on arm and on system 390. And containers. So they are explicitly listed then there are others where we say we'll we're willing to consider patches but we don't test them. We don't actively test. And we may drop support without telling anybody 32 bit for instance, risk five other exotic architectures like MIPS. And then any version not supported by the vendor. So we don't support. So did that answer your question on the meaning of support. Right. Yeah. Yeah, this was one that was vetted. Originally I think Oleg Nanash have created this Linux support policy page and made very was very careful to be sure that people understand this is not any statement of the existence of a support organization. It's rather that here are the things we test and here are the things we don't test. Yeah. Go ahead. Oh, no, I just said nicely done. Yeah, so so the idea but this page will certainly be linked from the blog post but I think maybe I will just make this redirect. Go to the blog post so that people also then have a forum at the bottom of the page that they where they can have more conversations. Good. All right, let me make a note of that. Are there people out there who love Santos seven and. Oh yes, absolutely well and there are companies out there who say the only thing you can use is Santos seven and and they largely don't care that it's reaching end of life. It's, they've chosen it all those years ago and they, they expect you to keep using it and the answer is, you're free to keep using it we just won't support it. Right. Great. So that was all the topics that I had for today Meg any other topics for you. Nothing for me. Okay.