 Hello, and welcome to Jenkins documentation office hours. Today is October 12th, and this is the EUF edition. Today we have myself and Bruno Verrachten, and Mark Waite shows up, shows up. Anyone else who shows up, great. Welcome, everyone, as always, and we'll add their names to the attendees list. For the agenda today, some updates on the Google Summer of Code, since that's now completed. The prototype removal from Jenkins. Oktoberfest 2023, Jenkins governance elections 2023 as well. The ongoing Java discussion that we've been having in regards to 11.17.21 and what Jenkins supports. Quick note about DevOps World Tour, and the process of choosing a plug-in bomb. Is there anything else that you'd like to see on the agenda for today, or does that cover things? If we have time, maybe we could just discuss the PR of mine, same-less-plug once again, regarding the use of update CLI to change a few Jenkins versions in the choose Jenkins version page. OK, yeah, sure thing. Is there, sorry, do you have a link by any chance? Yeah, I will give it in the chat. Sorry about that. Let me check. No worries. OK, yeah, no worries. I just want to make sure that we have, if we want to talk about it, we have time. Yeah, sure. Make sure it's on the agenda. Yeah, so OK, so we'll put that on there as well. We can put that, frankly, since the plug-in bomb hasn't had any progress yet, and the improved plug-in tutorial instructions do have that update. That's the same thing that we've been discussing for the last couple of weeks. So we could probably put it above that, if anything, too, and make sure we have time to talk about it. But yeah, anything else beside that one, Bruno? No, thank you, Kevin. OK, yeah. And is it an issue or a pull request? No, it's a pull request, and I'm searching for it. Yeah, I got it. It's a 6755. I will copy the link in the chat. OK, great, thank you. If I find the right button. There we go, it's copied now. Thank you. OK, beautiful, thank you. So just some notes on the Google Summer of Code, so this is now completed. All projects completed successfully. Really great job to all the participants. Thank you so much for all of your work and effort. This is great. We saw so much progress and so much care, work, efforts being put in. It's really nice to see. So we've got the version documentation for Jenkins.io, so the version documentation for the site. So this is looking really good. Chris has built a great demo site along with Andit. And at this point, we're just talking to the Infra team to decide on details, next steps, et cetera, et cetera. Bruno, any insights on the version documentation stuff? No, as far as I know. Everything is going smoothly. It's not finished yet. There are still some problems with the blog, I guess. But it's progressing. Yeah. Yeah. And I know that the events page still has a little bit of work to go. But the major building blocks of the version site are there and working. And it looks really good. So yeah, really fantastic. So then, yeah, so all four projects were completed successfully. And then there is still some work pending for the Gitline plug-in modernization and composing version documentation, testing more automation, just making sure that this is all going to coalesce properly when it gets pushed live. So yeah. Yeah. Getting a personal repo, even a public one, that kind of works for Google Summit, of course, is kind of easy, but integrated into the existing Jenkins.io, Jenkins Infra organization. That's a whole other story. Yeah. I mean, that's live rounds, so to speak. At that point, the Jenkins is moving, working constantly, being used by however many, like the exponential number of users that we have. The personal site is not anywhere near that kind of capacity or usage. So yeah, it's definitely a lot easier. Hello, Mark. Thanks for joining. We were just talking about Google Summer of Code and just kind of finalizing all that. Since Google Summer of Code is completed, the projects are really in really good spots and are at the point of how do we get these into the infrastructure at this point and what needs to be done to do that. So yeah, looking really good. Anything else on Google Summer of Code, Bruno, or Mark? That's for me. Thank you. More work to be done, but no, nothing to report here. Yeah. OK, great. Thank you so much. Something that, so we just published a blog post on this, but this also happened in last week's LTS. Prototype has been removed from Jenkins. So first and foremost, thank you to Basel for writing the blog post, announcing all this. And just as importantly, thank you to everyone for all the work that they've done in collaborating on this and helping to remove prototype. This is a ton of effort from a lot of people. Could not have been done without everyone's combined efforts. And this has been something that Basel had announced back in May that's been ongoing work up to this point. So to finally have it removed is really the culmination of all this, which is great. This will also be implemented in the November LTS, as far as I can tell at this point. And right now, 2.426 is actually the baseline choice for the next LTS, as far as the developer thread goes. So right now everything looks like it's going to sync up nicely. On Hacktoberfest 2023, so it's in progress. We're October 12th, like we said at the beginning of the meeting. And compared to last week, HavocC has reported that everything's basically at least double, which is amazing. Going from 125 PRs to 377 for Jenkins CI and Infra, amazing. Total Hacktoberfest PRs is 153 compared to 55 last week. Validated is 114 by 36 different contributors. We now have 20 more contributors than a week ago. These are all really fantastic signs of what's going on in Hacktoberfest and definitely what we want to see. The spam rate's been much lower than previously, which is great to hear as well. However, contribution rate is a little bit lower. But this is a sentiment that's being shared by other projects as well. So this does seem to be a trend of this year as opposed to something specific to the Jenkins project. Hackadays were also just happening recently. There's been a lot of stuff going on lately. Some folks may just be burnt out, who knows. But the good news is we're getting a lot of work done and a lot of progress for Jenkins. Actually, before I move on, Bruno Mark, any other Hacktoberfest notes to share or insights? No, well, so spam rate is still there. And we accept that not always willingly, but there is still spam. We filter it quickly and hope to keep on. Thanks so much, Mark. Next up on the agenda, so the Jenkins Governments Board and Office for Elections are officially happening. So this was announced September 18th. So voter registration and nomination periods have been open since September 18th and may close respectively on October 27th and November 5th. So there is plenty of time to register still and more of the time than that to nominate. If you have nominations, please submit them to the election committee group. You must join the election voter 2020 for your group if you do wanna participate. If you don't join that group, you will not be able to vote. And as last year, we're trusting that people are contributing to Jenkins and wanna participate because they're contributing. So there are tons of different ways to participate and contribute to Jenkins and be a part of the community. That's all the ways you can interact and join up is laid out right here. The caveat is that these participation had to have happened prior to September 1st this year. But outside of that, if you've contributed and wanna participate and be a part of the electoral process, this is a great way to get in. And there's more timelines here. So we'll look at closing the voting on December 1st and announcing shortly after that. And then in November, we'll have that voting period. So all five officer positions are open or up for election and then two board positions are up for election. Thanks to everyone who's served this past year. Appreciate it as always. And whether past term, I should say. And I've got a comment there. Kevin has been nominated as documentation officer next year and I'm asking for your vote as a board member. Thanks, Mark, appreciate it. And yeah, Mark, that's my vote for sure. No problem there. Next up on the agenda. So the discussion that we've been having for the last several weeks regarding Java 11, 17 and 21 for Jenkins. So we've got the Google doc that we've been referring to. The timeline diagram as well, which we've showed and provided some insights for. So the idea is two years of having the last Jenkins version supported or the two years of the version supported not required. So for right now, for instance, that would be 17. It's supported but not required. And then two years have required where that would be the required version and then two years where it is unsupported. The next version would be in that two year supported but not required timeframe, I think at that point, Mark, if I'm not mistaken. Or am I missing, am I messing up the timeline on that? No, you're correct. Okay, great. So it's two years supported but not required, two years not, two years required, and then two years dropped. No longer, no longer works. Right. And then, and that's visualized here. The blue is the required and then the orange is unsupported. So, and that puts us in sync with Java and the other OS and platform supports. So Microsoft, Demeran, everything with that will all line up accordingly as well. And then, so that will have more information and more details to come. There still needs to be a Jenkins enhancement proposal submitted for it and once that happens, we'll be able to really have a concrete place to put things and have a discussion and move forward. DevOps World Tour has been going on for the last month or so. Our next stop is Santa Clara, California, which is gonna be next week, October 18th and 19th. Mark will be there giving us talk as he has done at the Chicago and New York sessions. And yeah, there's still time to register if you haven't yet. The site is up and then we'll still have the Singapore and London dates after that as well. As we had discussed really quickly earlier in the meeting, so the choosing a plug-in bomb has not had progress in the last couple of weeks. The improved plug-in tutorial instructions does have the update to choose the plug-in bomb, but beyond what we've already discussed previously, there hasn't been any further progress on that. And then, Bruno, I'll throw it over to you because you wanted to take some time to discuss the update CLI. I'll be quick. Yes, thank you, Kevin. It's more or less linked to the choose a plug-in, choose a bomb and choose a Jenkins version. We already have something using update CLI in order to keep up to date the improve a plug-in tutorial when it comes to choosing a Jenkins version, choosing a build of material version also. But we have a page in the Jenkins.io website where we give advice about how to choose a Jenkins version. And up to now it had been generated via a Ruby script that runs each and every time we merge something into master. So it's working beautifully. The versions are correct, but as we are going to have in the coming months version, Jenkins.io website, I don't know if that still makes sense to have a Ruby script running whenever it runs and just update the documentation without touching the GitHub repo corresponding to that Jenkins.io website. So I just proposed to use update CLI in order to have a change log of what happened and when we change. So to me, it makes sense, but it doesn't make sense to everybody. So I wanted to talk about that in this meeting just because I'd like the community to give feedback. Should we go this way? Is it a bad idea? Or, you know, is there a better way to do that? So I like the idea of using this to track changes being made in that sense. That sounds really, that's hugely useful. And I can imagine where that would be valuable to anyone building or using Jenkins. I mean, I don't see, yeah. I don't see a downside to any of this whatsoever. For the end user, it wouldn't change a thing until we switch to a version Jenkins.io because the Ruby script already works, you know, so no value added as for now, you know, except that you get to change log into the repo so that you know when you change the version for whatever reason. And frankly, even one of the sources I used to keep that up to date hasn't changed in a while. It hasn't changed since Jenkins 2.346.3. So it's been quite a while. It won't change tomorrow. It's each time Jenkins part is extracted from the core and made as a plugin. So the last time it happened was on 2.346.3, if I'm not mistaken. And this file is also human maintained. So it may be wrong in the future, you never know. We all made mistakes, I do mistakes on a regular basis. So anyway, yeah, that's all I had to say about that. I'm not force pushing. I just wanted that we discuss that. We as a community, not the three of us. Yeah, of course. So with this idea, Bruno, if we were having versioned documentation on Jenkins.io and then update CLI is gonna update the version within the documentation based on which versioned page it's on. No, if I'm not mistaken, update CLI will only update the master branch. So whenever you will create a version and archive it for Jenkins.io, you will get in this archived version, the fixed version that was up to date when we created that, you know, only the master branch will change afterwards. So a big CLI won't touch any other branches corresponding to outdated versions of the Jenkins.io website. If I'm not mistaken, Mark, am I right? Yes, you're right. Gotcha. At least that's my assumption of how update CLI works. That's what I've seen in every other location and where I've seen it used. Is it limits itself to the master branch or it submits pull requests against the master branch? Yeah. Okay, great. So then, yeah, so we'd be able to manage everything accordingly after the fact too. And it wouldn't change anything that's not on master. So. Hopefully. Great. Yeah, ideally, of course. Cool. I mean, I think that's great. Like I was saying before, Bruno, I think having a change log that showcases all of those, even if it's not super, you know, in depth or doesn't, you know, go through every last piece of what changed, it's just having the fact that it changed this date at this time is huge. That just lets us pinpoint those kind of things, which is amazingly helpful. So, yeah, I like it. I think it's a good idea. I saw Alexander Brandes that also said, he said it's looking promising. So there's that. But man, I think this is a great idea. Obviously we'll have to wait and see the version documentation site, the version site. Yeah. You know, getting that into play, but no, that's not the end of the world. Thank you, Gideon. Yeah, no, thank you Bruno. I really appreciate it. Thanks for sharing that. And thanks for having that discussion here. So that actually covers everything that I had on the agenda for today. Mark, Bruno, anything else you want to add or discuss while we're here? No, thank you, Kevin. Nothing else from me. Okay. Oh, no, I take it back. I take it back. Yes, one more thing. I'm cancelling Doc's office hours tonight because I have a personal scheduling conflict. And it's canceled. Asia office hours is canceled next week because I'm out of town. And so, and I think it may be canceled the following week. So Doc's office hour Asia may be on three week, three week empty period. No, good to know for housekeeping. Yeah, we'll be back for Thanksgiving. Perfect timing. Great. Cool. All right, thank you very much, Mark. Appreciate the note. And yeah, thanks to everyone. Appreciate it as always for joining us. The video recording will be available in 24 or 48 hours. And until next week, take care. And stay safe. Thanks. Thank you. Bye-bye.