 Welcome everyone to the Jenkins docs office hours. This is the European edition on July 14th, Thursday. Today we have a few action items to review, some news about things that have been released, things that are coming up, and any updates that we have for some of the previous topics that we've covered. And of course, with our Google Sum of Code projects going on, we have Vahan here who's working on some wonderful things that he'll be able to share some updates on as well. So let's just go ahead and jump right into it. First things first, Mark, if you wanna just share where you're at, first status goes on the mailing list and the blog post. Yeah, so no progress on either of those. Sorry, they'll have to wait for our next session. Okay, that works. Thank you very much. So some things that happened this week. So 2.346.2 was just released yesterday. Everything went smoothly, successfully, completely. And one of the highlights that this actually brought along with it was it replaced the install plugins shell script with direct pointer to the plugin installation manager tool. So instead of relying on the scripting, they now have a direct interaction. They have an actual tool to use so that it just makes life a lot easier. And then 2.359 was also released. This just includes updates for more regarding the Java 11 update. And in addition to that, preparing for the Jetty 9 to Jetty 10 transition as that goes along right with the Java 11 requirement. Basil Pro is still helping us work on that and doing some work on that side of things. And as we get closer to having that completed, we can provide more updates. In addition to all of that, this DevOps world is coming up in September. Really looking forward to it. It's gonna be a really wonderful time. And there's a lot of great stuff planned already. The 27, if I'm not mistaken, is the Jenkins contributor summary. And where it'll just be a place for any Jenkins contributors to meet, talk, get faces, but to those contributions. And just be able to make those connections that while we have them online, now we can make them in real life as well. So it's coming up in, like I said, September. Registration is open now. And there's a lot more information available on the Jenkins.io site for DevOps World 2022. Mark, do you have anything to add about the Jenkins contributors summit and DevOps World before we move on? Bruno's leading the agenda work, preparing it, he and Alyssa Tong. We've got some really good topics and we'll continue announcing that publicly. Bruno, anything you want to share there? No, I'm afraid there's nothing really available for the time being. So maybe next week, I should post on community Jenkins.io the prepared agenda. But for the time being, no, there will be surprises. Thank you. Thank you very much. So next up on our list, our agenda today. So Vihana, would you care to take a few minutes and tell us any updates, any progress, anything that you've had with the projects you're working on? Sure. So since the last meeting, I have worked on completing the tests for the pipeline mirror-related results. And the tests are not complete from my end. They require some review because it's a slightly big PR. So waiting a review from Christian. And once that gets merged, we will release that artifact since CD is not set up yet. So we'll have to do it manually. And after that, we can finally use that inside the main repository, which was the end goal. And after that is done, I think we can also try moving the main repository from Java 8 to Java 11. And that would probably mark the end of my coding phase one. And we have our midterm evaluation on 21st July. So that's a meeting there. So then I hope to close this up and maybe add this to my work done list. So yeah. Awesome, thank you so much. Is there anything you just wanna show or share? If not, no worries. I just wanted to make sure you have the opportunity. If there's anything neat that you wanted to put out there for us. Nothing as such, everything's good. Okay, great. Thank you so much. And just as a side note too, Vihon, the pipeline steps reference page with the filter, the search filter and everything, really, really great. I actually was able to show it to some of my colleagues on the documentation team and just like how wonderful it functions and helps to navigate the page in cases where there's a lot of information on the page. So thank you so much for, you know, just making that a reality for the Jenkins documentation and for everyone else. Glad to hear that. Thanks a lot. Of course. And then one of the topics that come up in the last week or so is that Gavin Mogan, one of the Jenkins Feminist Board members has proposed that we create a new commercial support page for our vendors. As of right now, it's a little bare bones, but he's actually gone ahead and put a small prototype together. And just to see what it looks like, it's a lot more streamlined. It's a lot cleaner looking. It's much better designed. But the effect that you can also filter through different offerings from the vendors themselves helps just narrow down these results and get people to where they need to be. Some things that we've talked about before as well as having this filtering and offerings, direct links to support so that there's less, that many less steps for the user to interact with before they get what they need. And just being able to filter through and share what the vendors have in a more refined way, more clearly separating out by things like support or training or other like custom builds, making sure that this is all very clear. And so compared to what we have right now, that's a miles better. It's night and day difference looks wise. But yeah, this is something that I would definitely recommend checking out if you have time. This is something that any feedback is welcome for. This is a community undertaking. So more feedback and information from the community would be just super appreciated. And this is obviously a work in progress. So any idea is a good idea. And then there's also a separate look and feel PR that was submitted. So now this is a suggestion to update the Jenkins site as a whole. Things like the background, things like the nav bar and this user was able to actually go ahead and make the changes and review a lot of the suggestions that were made. So now we can actually check it out. And this is what the suggested Jenkins page now looks like. I was able to take a look at this with Mark earlier, but the new background color, the navigation, a lot of this stuff looks really nice. There are some pieces that need to be reworked such as the video player being a little too low for the screen fold, at least on my monitor. And just making sure that the other sites will function in the same way or have the same impact. Going from the main Jenkins page to plugins does not offer the same background, but that's something that we'll figure out as a community and check in with Gavin Mogan about since they'll be able to confirm a lot of that for us as well. Yeah, so Kevin, could you on this page and navigate open the documentation link and let's look at a pipeline actually while we've got Vihon here. Let's be sure that, so pipeline steps reference on the bottom left of the resources section. Okay, and does the filtering still work? I assume it does. So check out or yeah, milestone, perfect. Good, all right. Yeah, and it's a nice transition. It looks really clean and smooth across all of the Jenkins direct documentation blog sites. The plugins, like I said, are a little different and communities still got the black bar, so. No, no, okay, so there you just suffer the transition. So go back and that's okay because plugins does that. So now from here, click community. Okay, yep. So everything actually is all set there. Is in this case then Mark, is it really just the plugins page that's separate from all these? It is, and we know that the plugin site is a different site in terms of how it's managed and how it's maintained and therefore it needs extra thought. Could you click the download button just as one more check over the top right hand corner? Yeah, sorry. And it does, it still looks fine. Good, okay, thank you. Yeah, of course, thank you. And yeah, one of the things too just as a, to make sure they can know what was the font was a little changed or was changing the initial suggestions. So they went back to the correct font for four Jenkins and it does look that much better just having the right font sizing and formatting there. So yeah, there's a lot of great stuff being suggested for the community and for Jenkins as well. If you want to review them yourself, this is these links are here in the office hours notes to make sure that they're available. Definitely check it out. It should share any feedback that you might have if there's any suggestions for things like colors or any other navigation points or anything you think of by all means everyone wants to know and you feel free to share that. The other thing about the suggestions is that the English language site works fine if we switch to the Chinese language version it's not working right now. So we have to determine whether or not that impact is going to be secure enough or if it's even gonna be of concern at this point in time. So again, things that will be figured out once we get a little further along our math. Coming up in the next month, we have the 2.346.3 Jenkins LTS release. The change log and upgrade guide are going to be needed as usual and August 10th is the expected release date right now. That work has not been started yet but we'll be starting it shortly. Tinge Home will create a start the thread for the release leads and we'll get everything sorted out on that front to have the change log and upgrade guide ready to go. Could you Kevin, could you add to the notes there? Yeah. In our session on the 2028th, we should review, so January and July 28th, we should review the change log because by then there should be, usually we'll have the pull request ready by the two weeks prior to the release. So it will have been just barely created by that point. Okay, great. Just great. Is there anything else on the 2.346.3 release mark? That's it for me. Okay, great. And yeah, so we've brought this up in the last few weeks but with the requirement for Java 11 in the weekly release line, the LTS release is going to match that in September and at that point in time, the Java 11 requirement will be part of Jenkins as a whole. There won't be any difference between the weekly releases, monthly LTS and so Java 8 will no longer be supported at that point but we're getting ahead of ourselves now to make sure we're getting out ahead of it now to make sure that people are aware and that this is not as prized when it happens. I've gone through some of the existing documentation for Java and updated it to explain that fact and point out that there is slight difference in the time being and once the LTS actually is released, we'll be able to go back, I'll be able to go back in and update those so that it is aligned on just the Java 11 aspect of that. So a little bit of a difference for now but it's going to catch up and when that happens we'll need a new change log enough for a guide for that of course and we'll start figuring that out, I'm sure in the earlier parts of August if not a little after that. So more details will be available as that comes. That covers everything we have on the agenda. Mark, Bruno, Bihang, did anyone have anything else they'd like to share or throw out on the agenda to discuss? Nothing for me. I will thank you. All clear. Great. Thank you so much. So we'll stop the recording in a second and then you'll be available.