 Okay. Welcome to Jenkins documentation office hours. Today is March 2nd. This is the U.S. E.U. edition. Today in, as far as attendees go, we have myself, Bruno Rockman and Mark Waite. Thank you for joining. And if anyone joins in while we're going through things, we'll welcome them as well. On the agenda today, I have a few action items, just some new blog posts to mention and point out. Specifically, Bruno's newest one that we published this week. Updates on the week leave of this past week and LTS 2.38, 7.1. Some talk about the Jenkins Awards 2023. There is some timeline that we want to talk about. The nomination is closed tomorrow. Documentation transition to drop of 17. And what that might entail look like. Improving end of life notifications. So when we do get to end of life of some of these platforms, products, different softwares, we can go through and make sure that everything is updated and modified accurately and correctly. And then talk in addition to that checklist to make sure we're going to the right places. Places that we might not think of right off the top of our head. Or just in general, good places to look for anything that needs updating. Some preparation for the center 7 end of life. This is Mark's proposal and something that we've been discussing for a few weeks now. So just more discussion on that. A couple of quick updates on the Google Summer of Code prep. And if we have time for it, just a couple of notes on adding books to Jenkins.io and what we can do to help people who want to make those contributions. Is there anything else that you want to put on the agenda? Or does that cover things for everyone at this time? Okay. Sounds good to me. Thanks very much, Mark. Okay. So first things first, again, some blog posts that we've had published recently. We have our Fostum recap, which is really wonderful and lovely and was created by all of our Jenkins attendees to Fostum. So lots of wonderful insight and experiences and stories to share there. And some really great photography as well. We published the Google Summer of Code participation announcement. So Jenkins has been announced as a participating organization for mentorship. So that's just us celebrating that. And it contains links to other pieces of Google Summer of Code information, tips for mentors, contributors, proposal ideas, et cetera. We also published a blog post announcing the CD Foundation Awards. So these are now being hosted by each project individually if they've graduated to that level. So that means us and Tecton, I know for sure, have their own awards that we're hosting. These are being hosted in the Jenkins.io repo. So one of the biggest differences between this year and last year. And we'll talk more about that in just a moment. And then lastly, this is, again, the blog post that we have published this week. This is direct from Bruno and how to build an unsigned Jenkins MSI on your Windows machine. Bruno, is there any sort of elevator pitch or anything to say about the blog post? No, I'm afraid it's really straightforward. It's a no brainer. Just copy and paste. And this should work for you. You know, when you don't know yet how to build one, it's kind of difficult. But once you follow the instructions, frankly, it's pretty simple. And I know it already has helped one people. So goal reached. Thanks for your help in reviewing that short piece of documentation, Kevin. Yeah, of course. Thank you for contributing it, Bruno, and adding it and providing that knowledge. It's a great, great ad. And yeah, if it's already helping people, it seems goal accomplished, like you said. So that's awesome. Thank you. Okay. Next up, we have our weekly of this week, which was 2.3.93 that went successfully. Change a log has been updated and merged accordingly. So that's up to date for this weekly. And we'll continue the same process as we go forward with it each week. We also have our next LTS releasing on March 8. So next Wednesday, this is going to be version 2.387.1. So a very large change log that's included due to all the changes we've had since 2.375. I have submitted that and the upgrade guide for review. I've included screenshots of the preview for the change log. And Alexander Brandes has already provided review and feedback suggestions, which I've been able to apply. So we're in a good place with that. Lots of good feedback there that I've been able to apply. And one step closer to having that ready to just be merged. Mark was willing to do his review, but he's aware of it. So I'm not gonna mention that again. But yeah, any notes on the LTS release mark or anything else that we should be aware of? No, just the the urgent action that we've got to have a change log and it needs to be well reviewed before we ship that thing next Wednesday. Thanks for writing it. Sorry, it hasn't been reviewed yet. No, that's okay. It was pretty recent. No worries. Cool. Next up on the list are the 2023 Jenkins Awards in conjunction with the Continuous Delivery Foundation. So we have three awards. We have the most valuable Jenkins contributor award, the Jenkins Security MVP Award, and the most valuable Jenkins advocate award. We're hosting these, like I said, in the Jenkins.io repo. And to contribute a nomination or submit a nomination, all you would need to do is go to the respective award you'd want to nominate for and provide a comment here explaining who you want to nominate and why. People can, you know, voice off in the comments or the emojis and respond to it, let people know that they're in favor of this. I'm pretty sure there's a lot more nominations on the Jenkins advocate. Yeah, so we are getting some action on here. And we'd love it if more of the community would participate and engage as well. If there's someone you can think of that you've worked with, by all means, feel free to highlight them here. Even if they aren't winning it, it's still nice to know and still great to have that appreciation coming from anywhere. The nominations are open until tomorrow, Friday, March 3rd. So you do have time between today and then to submit those nominations. And then when the nominations close, voting will take place later via Google Form. And that'll be distributed and handled by both Jenkins and the Continuous Delivery Foundation. So more details come on that. You do need a GitHub account to vote and nominate since the issues are in GitHub. And something to note is that last year's winners cannot win the same award this year. So Basil cannot be the most valuable Jenkins contributor again, despite how I might feel about that. Jenkins Security MVP. So Wadak, unfortunately cannot be MVP again there.