 Hello, and welcome to Jenkins documentation office hours today is November 2nd And this is the Eve US time zone in addition today We have myself and Bruno rockin and mark if he joins us we welcome him as if we will anyone else if they show up Otherwise, thanks for watching on the agenda today. We have Some just another note on the version documentation for Jenkins.io The plug-in health scores blog post that Adrienne wrote Another blog post from a new author by the name of Mark Phillips on updating Jenkins. I Wanted to just highlight a couple a few small pull requests that were submitted by new contributors Prototype being removed from Jenkins and the next LTS baseline is going to be releasing in a couple weeks Jenkins governance and officer elections for this year October fest 2023 since we are now in November and October fest has officially concluded. So we have some stats on that the the Java enhance the Java support plan for Jenkins and the JEP that has now Been submitted as a draft for mark The update CLI discussion which we've been having for the last few sessions and the October newsletter She's currently being compiled and we're looking to publish next week Anything else that needs to be added to the agenda No, nothing I can think of. Thank you Kevin. Yeah, good. No worries. Like I said If mark does join us and he has anything to add we'll make sure that gets on there as well But we'll get started. So First thing on the agenda is the version documentation site for Jenkins.io This is something that we've been discussing for quite some time now No new updates as far as status goes but Just to touch base again on this So Chris has started the conversations with the info team to figure out the next steps for that and getting that going They're preparing the entour a site to be hosted for the version documentation and kind of the next steps They need to take before that's really official And there is prototype site that Chris and Vandeet had been working on that does showcase the entour build of Jenkins.io So same information as before but just want to keep on top of that Next up is the blog post that we published recently by Adrienne So this is just the announcement blog post for the plug-in health score It's now available on the plugins dot Jenkins.io site on every plugins page It's in its own tab that says health score if I can zoom in here We'll see it a little bit here, but that's a new tab that's available on every plug-in every plug-in scored and graded in the exact same way So it is consistent across all the plug-ins within Jenkins ecosystem And Adrienne has provided this blog post that goes into more detail and explains some of the logic and reasoning as to why that's gone on And and how it can help you Next on the agenda we have another blog post from a new author named Mark Phillips and he wrote a blog post on the guide to updating Jenkins For the uninitiated sounds like me a lot of the time But yeah, it's a great little blog post that just details how to update Jenkins and what that means Some great steps just some great writing here and a really lovely contribution from a new contributor by from Mark Big big thanks to Mark and thanks to Bruno for actually helping get this published into the Jenkins site He helped with getting that put together and submitted as pull request. So yeah, thank very much, Bruno You're welcome Mark is active on the community Jenkins.io website, but is not active on GitHub yet You know he even doesn't have an account. That's why I had to help But I'm super happy to have him as a first-time contributor That's fantastic. And what a great example of ways to contribute to Jenkins without necessarily contributing code or anything directly to Jenkins itself But being part of the community answering questions helping guide others. That's a really really terrific example of In a little bit more out of the box for contribute contributions. So that's really great to hear And hopefully we see more from Mark Next up there were a few smaller Updates for the Jenkins.io site in the case of documentations I just wanted to take a moment and acknowledge and highlight and thank these contributors They're newer contributors to Jenkins even if they're working on other projects and again, these are not world-changing updates necessarily but Folks are taking the time to go through and update some stuff that they didn't feel was right. That's great Taking it small starting small in an open-source project that you may not be familiar with Making suggestions that are not, you know game-changing or breaking but can have some benefit there These are the pillars of what a lot of folks recommend when it comes to open source and participating in an open source project So thank you to all three of the contributors for putting that work together and welcome to Jenkins Yeah, welcome. I think you spotted it You know start small and then iterate. It's a way I started with Jenkins Oh, there is a comma missing in this part of the documentation Yeah, my first comment. I was happy as can be and yes, it's a good thing to start This way and I hope to see many more contributions of these new contributors. Welcome Yeah, and yeah, I think I think it's nice that Chocases the sentiment like I would say I've been working with some of the heavier lifters in the community and in the project itself And they all seem to have a very similar line of advice of start small get into grids see what's going on kind of like Get your feet wet, but don't don't don't feel like you need to jump in in that way So really nice to see and just really great to have that exemplified in this way Okay, next up so prototype JS has been removed from Jenkins as of weekly 2.426 We've been discussing this for a few weeks now Basel wrote up this blog post explaining that back to the beginning of October, which is great. Thanks to him for writing this up And the everyone that's worked on this to get the prototype removed from the various plugins on Jenkins There is a tracking sheet here in the original blog post that we have that does have all the plugins that have been updated and adjusted so There are a couple that still need to be have need to have prototype removed But we have got issues were created for those and we are it Basel has gone out of his way to Check in or at least try to connect with the maintainers of those plugins to get that taken care of We may need to give him a little push, but the work has been done And yeah, this will be implemented as part of the November LTS release as well So that'll be speaking of the November LTS release. So LTS 2.426.1 will release on November 15th So just a couple weeks away I've created the pull request for the change log and upgrade guide already The upgrade guide does need to be updated It's going to include the prototype information along with the list of plugins that still need to have updates And it's the change log itself was going to have include a banner Because of all the recent changes and updates with Java 17 You just want to make sure everyone's aware of those things So there will be a banner similar to how there is one right now for two for four one four dot three That'll just give a couple quick notes about hey We're using this as the default if it's not specified these tags are no longer working These are the new tags you need to use that kind of stuff But the upgrade guide does need some more edits to be made the change log at this point in time should contain all the backports and issues So I think there was one that was just merged a couple days ago That wasn't originally part of the candidate list, but now included so Even that's been that's in there. So we should have everything we need on the change log itself Obviously Any further review feedback suggestions or changes are able to be made until that release And I am welcome and open to all all of that Next up so Jenkins governance board and officer elections for 2023. So the nomination period did close this past Friday Voter registration period is open till Friday this this Friday the fifth Depending on the number of nominations we have for each Position the voting process may or may not happen Similar to last year where we did not have enough nominations. We did not hold a vote There was no need to since there was no way to vote for someone over another person This year may reflect that same process, but that will be TBD. So Keep an eye out for that in the next week or two So we're now like I mentioned at the top of the hour. We're at November 2nd so October fest 2023 has concluded as far as October fest 2023 goes There was a dip in participation compared to last year, but that is a sentiment that was felt throughout other projects Oleg who's one of the board members Said he had a similar experience with other projects that he's participating that he participates in So this seems to be a common theme The other side of that the spam rate was much much lower this year than it has been in previous years Which was great because that made everyone else's lives that much easier Not having to wade through all the spam requests or pull requests that are unnecessary or just down right wrong great As far as pure numbers and data goes so this year we had Over 1,000 PRs created so 1029 to be exact Um 415 Hacktoberfest PRs in total 81 different contributors for the hacktoberfest PRs 356 valid hacktoberfest pull requests and 68 validated contributors So yes, the numbers were a bit lower than they were last year, but it's a common place of other projects and The quality is really what's important here It'd be great to have all the numbers in the world and get those higher and have more participants But provided the participants pins we have the card contributors are doing really quality work The idea is to help them get acclimated to open source and You know, of course as a project we want to benefit from helping those people get acclimated. So We're getting the results we want even if it might be a little bit Lower than last year Next up so we have the java support proposal This is the jenkins enhancement proposal that mark has submitted. We've been discussing this now for the last It's been a little bit But the idea is that we're looking at a two plus two plus two support model for each java release Going forward that would mean we are supporting the release for two years, but it's not required. So Java 17 it is not required, but we are supporting it Then when java 11 next year java 11 is going to be end of life. So we're going to make java 17 required And then there will be a period where Right like right now java 21 is being supported And then once we get to the end of that two-year period with java 17 Java 21 will then become the required version and then java 17 will eventually be unsupported and so Within the enhancement proposal, there's been a lot of discussion going on around The different use cases that this could affect between enterprise customers or enterprise users and Early adopters developers small time or smaller scale operations They have different needs. They have different issues. They have different Points of contention or concern when it comes to this sort of plan So the two plus two plus two option is what we've come to find as a nice compromise in between the two where We're not supporting something that's so old that we shouldn't be anymore But we're also not forcing anyone to integrate new technology before they're ready Obviously, there's some still some fine points to come along with that However, this is a really nice medium that we've come to find and the discussion isn't necessarily about the proposal itself. It's about what kind of Extraneous issues could come up or what other concerns people might have when it comes to something like this And it's it's really come down to how conservative are we going to be with this warning? Is it going to be too far out? Is it going to that it's ignored? Is it going to be too soon that it's too much to do in the short time? Like that's the kind of fine tuning that we're looking at right now Which is like if that's the worst thing we have to worry about that's great news That means everyone is at least accepting of this this plan to support these in this way The nice thing is too that also lines up with the upstream support of these things. So When oracle supporting it when java supporting it when red hat supporting it all these other You know entities that are not Jenkins Are going to stop supporting these things at some point as well if we line up with that stuff everything's That much smoother in the long run. So really great Discussions being had I think the proposal is really nice Basil Crow is writing up a blog post that's going to share a lot of this with The entire community as well as discuss a little bit further about Some of the aspects of these java versions for Jenkins. So Looking forward to that and I think that'll be a really nice And digestible way to get this information out to everyone Next up on the agenda. So the update cli discussion. So this is again something we've been discussing for the last couple sessions here Essentially, the idea is that Bruno's created update cli to help with updating versions throughout the documentation of Jenkins and other Parts of Jenkins. So there's like blue ocean updates various Timurin updates Anything that basically has a version update. This is Designed to go and help and then What has been proposed is that we also would then have a log of Changes being made throughout the site where we don't have to go to the commit history or the get history of The site to find out when something happened and what that change was This will create a log that's much more accessible easily navigatable and searchable and and able to find out When what and where these changes were all happening We've discussed it before I think it's a really great idea. I like it. I think having a separate history would just be invaluable to finding out when something goes wrong or something changes and we need to revert back We have a process going on right now to remove some of the old and no longer used pages on Jenkins.io This sort of log would be perfect for that project because we're making changes in a lot of places We're trying to determine when something was removed where it was removed from This this kind of thing would help in determining a lot of that information Bruno anything you'd like to share point out make a point of on this No, uh, you sold it so well Uh, wow I couldn't have done that well. So no, that's uh, thanks a lot for your explanation. It's much more clear when you do that um Yeah, I'm just waiting for somebody to merge it one of these days or I don't know we I like it to progress if that's possible without putting the burden on anyone Uh, because I've got a few other ones um That depend on that so Yes, uh, it's um Continuous process. I have all the parts of the documentation to update after this one Gotcha, um, so, uh Let uh, I wonder if you can clarify for me then Bruno is if we merge this is there any Is there any concern with just merging it or uh getting it into the repo at this point in time? Or is it more just a we're looking for agreements and confirmation from others? I think we're almost good to go if you click on the file change tab I think I made some modification but that won't Get rid of the existing code Um, so that should be good. You know, it doesn't break the website in itself It will just create some code to make some new prs and if ever the prs are not helping or doing Nonsense, um, then we can just ignore them and uh, would work we can Revert my pr, but I don't think that would be necessary. We can just ignore, uh, the prs waiting for my Correcting pr Yeah, okay. Um Okay, uh, then Maybe what I'll do is I'll Double check with mark either today or tomorrow and just make sure. Um, I have no problem merging it myself I like I said, I like the idea and I think it'd be really useful to have Uh, worst-case scenario we get some pr noise that we don't listen to like you said Um, not the end of the world Uh, but yeah, let's get another bill of eyes. Yeah Yeah, basically, um And alex brandus has already approved said he likes it. So, uh, I mean that's a pretty good sign for me As well so Yeah, no reason to hold this off any longer if there's nothing of concern there and Yeah I'll take that one to mark and uh, just check with him about it Thank you so much Yeah, of course And the last so the last time I had on the agenda was the october newsletter This is currently being compiled and once it's finished being compiled will look to publish it when it's ready I need to update my section a little bit. So guilty Um, and I think there might be a couple other sections. So I'm not alone, but I'm not going to name names. Anyway So, uh, yeah, the october newsletter should be here within the next week or so And yeah, uh, there's some other stuff that's coming up For Jenkins down the pipeline not totally ready to share all of that just yet But really exciting look into our community and how How our community can inspire and enrich others with Just themselves That's a it's a really nice project to highlight some folks that deserve highlighting and I'm really excited to share that when we're ready Outside of that, I think we've finished up our agenda Bruno. Do you have anything else that you'd like to share or talk about? No, thank you giving them good Okay, so then in that case, uh, I'll go ahead and end the recording here. Um Video should be available in 24 to 48 hours. Thank you as always for joining and watching. Uh, if you haven't joined us Take care. Stay safe and uh, yeah, we'll see you again next week Right now