 Greetings and welcome to the Jenkins documentation office hours. Today is August 10th and this is the EU-US edition. Today we have myself and Mark Wade. Bruno is taking some PTO so he won't be with us this week and if anyone else joins up while we're discussing things we'll welcome him in. Today for the agenda, notes about just the one blog post we had published last week was our July newsletter. The weekly 2.418 release and a coming 2.414.1 release. Notes on the Google Summer of Code and where things were going there. Updates and progress made there. The topic of potentially moving some documentation to make it more easily accessible in terms of finding it and housing it. A couple pull open pull requests of interest. And then this is a discussion that we've been having now for some time. Mark's proposed the proposal for how we go about supporting Java 11, 17 and 21 going forward. The DevOps world tour and Mark is going to be out of office for some time and then I'll be out of office at the end of August so we'll discuss those once we get there. And yeah, so Mark just to make sure. Anything else to add to the agenda or does that cover everything for us? Nothing else for me. That's more than enough. Okay, great. So starting us off. So the Jenkins July newsletter was published on August 2nd. You know the deal is at this point. Our monthly newsletter. We got it out really early this time around which is great. New success. And yeah, just all of our wins from July and all the updates that we have for you from the sig leaders. Weekly 2.418 was released earlier this week. There were some issues in the build but it got straightened out and released no problem. So that is available. LTS 2.414.1 the new baseline is going is set to be released on August 23rd. The release candidate was is available as of yesterday. So download test, etc. The change login upgrade guide have been created and a pull request has been submitted for that. Something to note is that the upgrade guide is being adjusted still. There are a couple of issues specifically with the calendar view or the global build stats plug in in a couple of other items that are still in the process of being worked through. So there are for the most part it is ready to go and ready to be reviewed. But the upgrade guide may see some additional changes before it's before it's ready to emerge. So the story there is there are three cases where we're going to document that it's known that if you upgrade to this version with these plugins, you'll see you'll see a bug. Great. Yeah, and I actually just submitted an update for it is essentially explaining that on for the global build stats plugin specifically since that was a new one to add. So Google Summer of Code has been in full swing for some time now. The mid of term evaluations have passed all four participants have passed, which is great. And so we've got the version documentation for Jenkins.io, aka building Jenkins.io with alternative pools from Vandit. Vandit's going to demo that at the next UX big meeting, which is August 16th. And that's one that Christina Pizzagale will be leading. Others are certainly encouraged to attend. Definitely. And I know I'll be there. So yeah, we'll have we'll have representation and someone to ask Vandit some questions. Speaking of questions, these are some that have come up lately since Vandit's got the demo site available and looks really good. There are some things that obviously we can take and look at and discuss such as what versions are available for the documentation. Marks stated the baseline seemed like a good idea. Meg has agreed. I think that's a really good idea too. The weeklies happen so often and so consistently. And if there's not necessarily change between, you know, 2.416 to 2.417, is it worth having both of those versions separated and available like that? Or does it make more sense to have the bigger releases be that point of change and that point of, okay, here's where we can definitively say we're supporting something like Java 17 versus Java 11. So there's, yeah, I'm sure there's more nuance to it than something like that. But there are other questions that have come up. So is there a way to limit the number of releases displayed? What kind of, is there, Meg's got a really good question that she asked about. Is there a way to know that the information's changed on the page other than just looking at the version number or seeing, you know, what are the differences between the documentation and that might just require knowing what to look for at that point if there's not a dead giveaway. But just great questions to have and good things to think about as we're moving towards the finish line here for Google Summer Code. So great discussions being had though. The diagram proposed for tutorials that Ash Tosh has been working on still has some more work to be done, but looking good. Get lab plug-in modernization from Harsh. There's still some things that need to be tested and determined for that. Mark, do you have any other notes on that one or any other insight on that? No. Okay. And the plug-in health score that Jiguri has been working on is still moving forward. So great work there. Thanks to everyone for their constant work. Like we mentioned, the midterm evaluations have been completed as of July. The final evaluations, that period opens on August 28th and closes September 4th. So that time period at the end of the month there. And the final presentations for Google Summer of Code will happen in mid-September. There will be a webinar or some sort of presentation there. That'll be recorded. That'll be available. More details come on that though. The next item on the agenda is something that I actually just sort of discussion with Mark about. There are documents and pages that exist in the Jenkins documentation on Jenkins.io that are available in places like the installation guide, but don't necessarily have a proper home, so to speak, outside of that. So stuff like the support policies and Java requirements, Java upgrade instructions. These are things that are inherently part of the installation guides. So for instance, if we go to anything like Linux, the prerequisites have these links available. But beyond that, the only other way to find them is to search for them. So what I had proposed is potentially moving the support policies and Java requirements into the system administration section, where we can create a separate section for these support policies. And in my head, I thought they could work something like the reverse proxy configuration, where it does have a collapsible menu for the various options there. We'd have similar setup where it's support policies, and then it would drop down to reveal the Linux, the Windows, the server containers, etc. And then having a separate section for Java requirements or just upgrading Java. But the other discussion there is, well, we're looking to have an upgrading Jenkins section. Wouldn't the Java upgrade really well there? And so that's another, that would be a separate section from the system administration that we have set up though. Vandeet, I want to say had started working on that a little while ago, and just need some more work there to get that to a point where we can publish that. But outside of that, it's something that would be relatively easy, and wouldn't necessarily change anything about where everything is located currently. It would just give them a secondary home, so that it's not mess like people don't necessarily go to the installation guides after installing. They may not find need for it or have used for the installation guides post installation and setup. So just making it easier to find would be a win that we could get really easily. This is an ongoing discussion. I'm not trying to do this immediately. Just something that I have been thinking about as I'm working on stuff like changelogs and other documentation that from an outside user, it could be something that people find really useful. So by all means, any other ideas, comments, insights aside, like please feel free to share them here, posting in the docs getter channel. There's plenty of ways to communicate. So feel free. And then for the open pull requests of interest. So we very recently had one that Bruno had opened up, basically using update CLI to update tool versions in documentation throughout Jenkins.io. This has been working incredibly well and putting in a lot of work as it stands. There have been tons of pull requests coming in to update the tool versions. So just like this one here, there's still some, there's, there can be issues that need to be addressed or instances within the pull requests where something might need to be adjusted or fine tuned a little bit. But just the mere fact that we're getting these updates and these pull requests created automatically is a huge win. And if you go back to that page and click the pull request tab up at the top and then click closed, you'll see already at the very top a recent update that came in changing the Golang version. So none of us had to track that Golang had released a new version. Update CLI did it for us. And it's current. So thanks very much to Bruno. And this is using GitHub actions, which is something really nice and new. So that's always fun to incorporate. But yeah, this is something that Bruno created specifically for this. It's working like gangbusters. So yeah, it's super, super thanks to him for all his work on that. And then the other pull requests that we open pull requests that we have is the administering Jenkins and Kubernetes pull request. We just need some review from people with Kubernetes expertise. But yeah, we'll get that determined and get that reviewed and published when we have that. Next on the agenda is the proposal that Mark's created for Java 11, 17 and 21 support and what our next steps are. And I'll bring up the proposal, but Mark, I know you wanted to speak to this and discuss some points on this. Yeah. So there's just one item here. It is that we knew the second proposal in the Java 11 section. The first says October 31, 2024 is end of life for Java 11 and Jenkins. That had already gone out to the board and to the officers. The third proposal there, end of life admin monitor, had already gone out to the board and the officers and then discussed originally. The middle one is new. And it's saying when do we declare that Jenkins will no longer support Java 11 at all. And for me, my proposal was let's make it as close to the Java 11 end of life as we can without going beyond the Java 11 end of life. And so that means August 7, 2024 LTS release is, would be the last Jenkins version to support Java 11. So roughly a year from now. Nice. I mean, that makes sense to me. And that would give roughly two months prior to that LTS release that would require 17. If I'm understanding correct Mark? Well, yeah. And people can transition to 17 now, right? So we're giving, we will start warning them in a weekly in October and then in the LTS in December that Java 11 is going away. And Java 11 will then go away with, it will no longer be supported in the September, September 4 LTS release. So forgive the numbers. They're declared approximately because we can't predict what number will be selected as the LTS baseline. Of course, no worries there. That sounds, that sounds great to me. I mean, that makes sense. And yeah, the idea is to line up with the end of life and make sure that we're not going over, like you said, so makes total sense. Yeah. Cool. And yeah, and the, I mean, the idea is just that we're, we have a plan laid out for how we're going to support Java going forward for Jenkins overall, whatever the version might be at that point. So yeah, all right. Cool. Thank you very much, Mark. Thanks. Next up, so for the DevOps world tour. So again, this year DevOps world is happening in a different capacity in a different way. It's going to be a multitude of dates and cities that we have listed here. DevOps world is going to be multiple dates. Some of them have a couple of days for it, such as the September and October events, but others such as Chicago and Singapore are going to have one day dedicated to it. The idea is that it will be more mobile, more accessible for more people, as opposed to having it hungered down in one location for a few days. This gives folks the ability that or gives folks that might not have the ability to travel the ability to actually get to DevOps world for for a change and in person as opposed to virtually. So yeah, so the the goal is the same. The idea is the same. Everything's the same. There's just the execution is a little different this year. And Mark's actually going to be speaking at the New York, Chicago and Santa Clara dates. So that's very, very exciting. And then Olivia Lamian will be speaking at the Singapore date and Tim Jacome will be speaking at the London date. And I got that right this time because I got it wrong last week. So yeah, just a great chance to learn more, get in, you know, acclimated to the DevOps world, and a chance to just connect and meet some folks that may not have been able to prior. This is a great networking event. It's a great event just in general to come out and see what DevOps has to offer. So registration is open right now. The website has a lot of further details and information. And they actually also have a list of the talks and speakers and everything that's going to be happening. So by all means, check that out for more information and get a better feel for what's going to be coming up. Finally, on the agenda, so a couple of housekeeping notes. So Mark's going to be out of office next week. So the I'm taking it the August 18th meeting has just been cancelled at this point, Mark. I think I already canceled it. So yeah, if you want it back, I'll have to oh no, I did not cancel it. I take it back. I'm wrong. I'm definitely canceling the August 18 meeting, the one that is Asia office hours. But the this meeting can certainly continue. So August 18, Asia office hours is cancelled. This meeting August 17, no problem if it goes ahead. That's up to you. Yeah, I mean, it'll be happening. No problem there. Yeah, you US docs office hours are going to be happening as normal. So no worries there. And then this is actually something that I came up the other day, but I'll be out of office on August 31. So would would you be able to host Doc's office hours at day, Mark? Or would you bet I can do that? Okay, great. Thank you very, very much. So we don't have to do any other adjusting to the schedule. Perfect. Great. So that covers the agenda that I had for us today. Is there anything else you want to discuss or talk about Mark while we're here on the call? Nothing else for me. Okay. In that case, I'll we'll go ahead and wrap up for the day and give some time back to everyone. Thank you so much for as always for joining. Recording will be available 24 to 48 hours. And yeah, take care. Have a great rest of your day. Enjoy your week. Thanks.