 Welcome everyone. This is the European Docs Office hours for Jenkins June 23rd, 2022 edition. It's been a busy week for us here. So there's good, fair amount of stuff to talk about. And today we have the LTS, which just released yesterday. We had a blog post concerning a couple items there, the change log, the upgrade guide. And I know Mark was doing a stream just prior to this regarding some of the other items that came up with it, which is great. Then we have Johan here. So, Johan, you can give us an update on the Google Summer of Code and how everything's going with that. Any progress you've made with it with some of the items from since last week. And yeah, from there, we'll talk about the Java 11 requirement, which is going to be coming out next week with our weekly release line. And there will be a blog post that will accompany this explaining the reason behind it, and also announcing the sport for Java 17. And then if Alex joins us, we can talk more about the localization with crowding. But if he doesn't join us today, we'll just ignore that for next time. So, first things first, yeah, the LTS, like I said, came out release yesterday. And Mark, would you like to add some kind of additional context and details about the release and how everything's going. Looking promising so far haven't seen any issue reports coming to issues.jankins.io yet it did include a security advisory. The security advisory means that more users should deploy it more rapidly than even typically. So, we're looking forward to that. Now the security advisory also published a an incremental version of the preceding LTS LTS in case people weren't ready to adopt the new one. They also used a new version of the weekly in case they were already using the weekly version. Great. Thank you so much. Yeah, and from my side of things I was able to publish a blog post regarding the SVG icon migration, since that's going to be a big change that comes along with the LTS update. The changelog will address a lot of the UI improvements and modernization that's also taken place for this release. So there's a lot of great, great info out there on what changes have happened. Steve Hill is one of the Jenkins contributors that works on a regular basis. He serves a Jenkins administrator and he did a he did a blog post on his personal blog about his experience upgrading Jenkins through one of the earlier large scale upgrades guava. And he's applying similar techniques learning further and describing it sharing it as he goes through these kind of changes. He manages multiple Jenkins controllers across this company and has to deal with variation between the controllers it's an interesting, interesting place where Steve works. Very good. That's awesome. And that's also a lot of great visibility for what we're doing. So kudos for everyone on that. And then the spreadsheet that we included in the Jenkins tick, the Jenkins Jira ticket, just have the tracking for all plugins that have either been updated or need to be updated regarding this change, which Steve's also been able to share his blog post and share out which, if I'm not, if I remember correctly, he said it was very helpful and just kind of identifying all these things and making it very easy to recognize and act on. So, wonderful. So, would you want to give us an update on the Google summer code project. Sure. So, after last week, I was able to get the second product first in which was the plugin list on the Jenkins a pipeline steps reference page. And then we discussed that we can include it for now and we can wait for some feedback regarding that page if the users want to get anything changed for that or perhaps even get it to move. We can wait for that. And then we think that we can include that particular feature on the set reference page so that was for it. And then after that, in the pipeline step stock of officers Christian explained me the working of the plugin manager that has been mocked from the Jenkins instance so that that was something very interesting. Since then, I created a couple of pull requests for the pipeline step stock repository. The first one being about separating the declared declarative steps generation from the main class, which is something that Christian thought would be better to do. And the second one was some minor refactoring things so both of them were pushed today. And for the next week, the agenda would be to get the data type on the parameter details on the heading as I discussed in the previous office hours. And after that, one of one of our goals would be to separate the entire hyper local plugin manager from the repository. And that is to create a repository for the plugin manager itself that can be used by some other other classes, other repositories in Jenkins as well. And that would be just imported and used for the pipeline step stock generated cost is something that we think should be present as a global feature so that others can use it because there's some really nice things happening and as Christian said, this could be helpful for the rest API generator as well. So getting that plugin manager isolated and functioning independently is something which would be very cool. So yeah, that all sounds wonderful and is there anything that you can share as far or you wanted to share as far as any of this goes behind I can start sharing my screen if you want to share yours or if there is pull requests that you would like us to take a look at or anything like that. Please file means feel free to share those either here or in Gitter or anywhere that you want to make sure they're available. So I usually link the pull request that are related to the website on the docs itself. So you can go ahead and find them and then over there. You can check out how it works using the deployment link. And like I'm getting some feedback from others like Tim has commented some things on that. I guess this is going quite smoothly. So if there's anything specific that that was in your mind to get to review today so I can perhaps present that particular thing. Yeah, I didn't have anything specific in mind behind I just wanted to make sure we gave you enough time to share and everything since last week we came up against the time a little bit. Okay, sure so I can I think both the pull requests are like ready to merge and you're just waiting for the release this week so I think we're good to go in that sense. Fantastic. So so behind I know that we'd reviewed the first request just to be sure that we've got the right ones so that the first pull request was where was it okay. I should just look at all the pull requests authored by you. Add independent scrolling in the documentation side by side bar that one been had been reviewed and I think we're ready to merge it. The other one I don't think has been reviewed yet the plugin list on the steps reference page. Do we okay but we do have comments there from Tim and from Daniel Beck. So, I'm not ready to merge the second one until we get we address Daniels Daniels observations, but the first one. Let's see did. Did we have any new feedback. No okay so I think, I think, well, I'm just going to go ahead and press the squash and merge button, because it's been reviewed enough we're at that point. It's now been merged. Great. That's that's fantastic. So there's benefit to attending Docs office hours you can inspire people to make changes because we're here. That's fantastic. And I think the pipeline steps doc pull requests are also rather straightforward to review and merge, and they keeping the pull request a little bit bite size so that it's easier for the reviewers also. So I'm, I think that that would also get merged. It won't take much time. Yeah so the that that one now has a conflict. So you'll you'll need to revisit it the conflict comes in from the, the changes that were just merged for the, your previous pull request so you've got work to do there. So I look into it. Thank you so much for on is there anything else want to share is or is that cover everything for you. Thank you. Great. Thank you so much. The next item on the agenda was the upcoming Java 11 requirement. So that is going to be part of the weekly release line that comes out next Tuesday June 28. So there's going to be a blog post coming from basil regarding the requirement. It's a very in depth, very thorough article blog post about it. That addresses why how everything up to making sure that it's installed properly and updated properly. So that's going to be very helpful it's also going to announce the Java 17 support as that will come alongside the release, the weekly release line. And then, Mark, would you be able to speak to the impact on the Jenkins core Java doc. It's the issue is resolved. And, and thanks to Basel Crow for implementing the resolution to the problem. It was, it was a, and there is more that will probably need to be done. Java doc Jenkins.io what you'll find is, it's a conglomeration of multiple Java doc pages it's got a top level page for the Jenkins core. So Java Java doc no C. Oh yeah. And, and so it's a this is a somewhat special case, the Java doc Jenkins.io site originally was just for Jenkins core. And we realized we really only need one URL, we could put all the plugins under that same URL so if you click Jenkins core you'll see the Java doc for the, a recent weekly, in this case 2.355, and it's rendered using Java 11 layout. So Java 11 layout puts that search, search field in the top right hand corner so Kevin if you search for file path for instance F I L E P A T H. You see, oh here are all the places that file path is used. And if you click one of those it will take you to that page so you get this built in search facility even though there's no search engine actually doing the work. That's nice capability. Now if you click in the top left hand corner overview. It takes us back to the top page that's not typical usually that overview would take you to an overview of Jenkins core. So that's, that's an oddity because we're placing all sorts of different components under the same thing that pick click Jenkins components. And here the one that has been updated is windstone so bottom the bottom most very last one is also using Java 11 semantic same look and feel no go back one page. And let's look at one that's Java eight like Jenkins test harness notice this one's laid out with frames. This this is Java eight it's got the old look the old feel as components switch to Java 11 they will get more and more of the improved layout. And that's, that's it it's, it's looking good yes there's more to be improved. Thank you so much. The last item was the support for Java 17 again that will be announced with Basil's blog post I've also been going into the existing Java documentation and updating that to make sure that that's included in our support. And also to make sure that the Java 11 requirement is updated as well. There will be some differentiation between the two until the LTS catches up with the weekly release line in September. At that point I'll be able to go back in and re redo the documentation to make sure it only refers to Java 11 upwards. So that will all be in the coming months and coming weeks so let's look forward to there. Did you have anything that you wanted to talk about or share in regards to, I mean anything that you've been working on. I haven't been able to work on the condition lately. And so I'm sorry but I don't have anything to share. No worries, just want to make sure. Thanks. Yeah, thank you. Thank you for asking. Do you have anything else that you'd like to add to the agenda I know we didn't get a chance to connect beforehand so that's it for me I think we're ready to be done. All right, great. Well, then if we're all set, we can stop the recording. And that'll be posted as it's as Mark can this. Yeah, I'm sure he has a couple of things on his plate so it might be 2448 hours.