 Welcome. This is Jenkins documentation office hours Europe Action items that I've got on the agenda for today Action items Jenkins elections end of December newsletter Actually, and I guess we should note November newsletter Because that's a good one to highlight end of December newsletter LTS 2375 dot one Thanksgiving blog post retrospective and I put interesting documentation poll requests and topics Anything else that needs to go on the agenda Bruno? Nothing I can think of thank you mark Okay, all right So let's talk about action items first then Archive the website component on JIRA so that we can focus on GitHub issues Alex Brandes has submitted a not a submitted. I think it was a ticket submitted to The help desk to the infra help desk So and I'll get that archive very included here. He put it in and I made a mistake of clearing his suggestion Here it is. Oh, why does it say rejected that was silly? Hmm, okay, I'll have to look it up separately. Sorry about that Okay, so the other Kevin archived the Docs mailing list so that one still in progress One that has made good progress not because of anything I did but because of what Basel did a poll request documenting the web application server support policy and It's a really nice piece of work that he's done if we look at it what you'll see is on The installing Jenkins page it now talks about the server container policy. Oh nice Included here and if I open up war files for instance a place where server container policy can be quite important Whereas before it only had Java web browser windows and Linux it now also includes a link to the servlet container support policy Okay, well though And it describes things as they are currently now in addition to what Basel did there he's also implemented tests to Check for regressions in case the known working service servlet containers were to somehow stop working. Oh So he's created automated tests that perform checks of wild thought wild fly version 26 and Tomcat version 9 I Think it's 9 Yeah, Tomcat 9 and wild fly 26 So deeply grateful to Basel for that work. It's not just that we've documented what the reality is He's also made it so that if we were inadvertently to regress We should detect have a better chance of detecting it. Yeah, that's great Fantastic, so That covered that one then anything else on action items No, no, thank you. Okay, Jenkins elections have been announced and the transition has started Alex and Uli Attended the last governance board meeting And they start we start on December 3rd. Am I right? That's correct December 3 2022 starts their term of service Officers and board members. Yes, exactly Great now the November so anything else on elections No, except congratulations for being elected Yes, congratulations to Kevin, that's good, I like also. Yeah Alright, so November newsletter Basel, thank you very much. So Alissa has gathered the content, right? Yeah, and I'm sorry Bruno, you have said the wrong yeah, that's okay It is so much of course when you think of something done, it may be basil. It must be basil. No, not this time Sorry, I did it It's not finished. She has a PR has been created and I have a few things to To change for example the highlights section, but almost done I think I'll be able to get it reviewed. Maybe tomorrow And so my goal is to have it published next Monday, so December's office Great, congratulations. Thank you very much. Thank you and thanks a lot to all the submitters who made Their section and you made two I think so Congrats on that too Yeah, I like the I like the exercise I was able to reuse content in both cases. It felt really great cool Anything else on November newsletter? No, thank you Okay, next was the end of December newsletter And what I had suggested to Alissa and she thought it was an okay idea checking with you as well was What if we made the December newsletter a look back at 12 months rather than just a one-month thing? I think that's great. That's a very good idea and we have so much to say we'll have to widely choose the subjects but You know, I'm not a long-time user long-time Jenkins user, but I've seen so many changes during that It's even not a year because I have seen changes from April I think but from April to now the changes are already major, you know going to GDK 11 then 17 even some part 19 and the UI UX has changed Quite a lot and some plugins are back from the dead Yeah, it's amazing all what has changed. So I won't How do we say that you know spoil? It's ember newsletter, but we have lots of things to say Good. Yeah. Well, and and let's see. Okay. So I've got I've got some for to include here. So Documentation site search improvement. Oh, yes, right. Just just one example and it's really thanks to Algolia and Gavin Morgan That the search engine works much better. I was should we phrase it finally works No, that's no it works before it had aged and it's no longer aged And it's now got a nice attractive experience. So yeah, they've they thanks to Gavin and to to Algolia very very much and Yeah, so we've got More topics, let's see So if if any if any come to mind by all means suggest them or propose them It would be a great thing for Alyssa or you and Alyssa or others to have to choose Which things they want to include in news that are based on highest value highest priority I see. Okay, we'll do Anything else on that that idea. Are you okay with that idea? I'm totally okay. I think it's a great idea. So yeah, let's go for it. All right so next piece was LTS 2.375.1 has been released and Now one of the the oops is here for us as adopts SIG was we had to revise the upgrade guide after release and what happened was I missed I Didn't do a thorough enough review of the source material of we had winstone 6.4 in the Baseline, but I believe then we did a back port of winstone 6.6 and That removed some additional Command line arguments and it was it's a really good thing because the the removed arguments had been deprecated for many years and It was certainly time enough to get rid of them with the transition to the new version of winstone Okay, so it's done that the arguments have changed name for example the Jaws They just disappeared. Yeah, right. That's cool Right and if you read the upgrade guide, you'll see the the description it talks about hey this one This one was these two were taken away and he do this one instead Or these were taken away. They previously did nothing and now they they still do nothing But they do nothing they fail because you can't use illegal arguments Okay, this case less is more cool, right exactly less truly is more The other is on a positive side 27 positive reviews on the ratings and no no I had issues and no rollback So that's good. Now we got a while to get before we get to 330 Yeah, yeah, of course Mark sorry to add that stupid question, but how do we enter? feedback for You know a new LTS version Because it's nice to see people are happy, but how does it tell us that they are happy or unhappy with the reads? So they click this link. Oh this image. It's a simple at that. Well, it is except Okay, so when I click the image it says thanks, right? Now I'm gonna go back because I don't want to disturb the measurements. I have installed 375 dot 1 So I happily can say yes, I've been pleased with it If I were to go back though and say oh, I want to report an issue that I found on 346 dot 1 so I could click the cloud and it asks for an issue number Okay, and for instance the you you'll see here. There are some issue numbers that are clearly invalid 1234 and 12 Are all invalid That's because we don't bother to attempt to filter Okay And you just entered one two, okay, right? So so and that's that's what's happened here, right? Someone said oh, I'm going to just play with this I'll click it and type in a number one two Jenkins one two three Okay, but that's nice It is the scoring the rating system is Is a sincerely a very valuable for people who are trying to choose more particularly trying to choose the next LTS baseline? because what we will do is we'll look at the ratings for the weekly releases and If the ratings are particularly bad okay, 380 is one that hey it had some really rough times and You see there's one bug that got 16 reports, and if we look at it It's this it's a performance issue that was just detected Okay, so that helps because we know okay if if 2.380 were chosen as a future LTS baseline We would absolutely want to be sure that the fix for this one was backboarded Mmm Okay, I was wondering for the previous month How do they know the health of a future candidate to be an LTS or not now? I understand. Thank you Right. Yeah, so the trick is we look backwards in time, right? So if we look at 2.375 Here's this one. This was the baseline for for the current LTS and we see All right, there are a few bug reports here, and I hope if we open some of them We'll see that it's fixed in This one doesn't tell me if it was fixed in oh Oh, this one is a complicated one. That's why okay, but we could we could try others And I suspect we'll see where it will tell us either. Oh, it was chill out chosen as a release as a Release candidate or nope. It was not selected and So this was oh, this was a change in In a plug-in. So that's another challenge is sometimes bug reports will be list bug IDs will be listed here That are for bugs that are not actually in core and therefore a core change can't fix it cool So did that did that help you see the the pattern how crystal clear thanks a lot for taking time to explain. All right Good So next next piece then I wanted to take a few minutes. We may want to delay this one week until Kevin's available because Very grateful for his work and Alyssa's work and air V's work And I think your work is well Bruno on getting the Thanksgiving blog post out I thought it was a good idea. I think it really was a good idea but it was Very rushed and it meant that we had two people in the US who are working on Thanksgiving Day a day that's supposed to be a Holiday, yeah, if I get that blog post out and and so it's just a reminder There's something to improve there, but I'd propose we just carry it forward into next next meeting And we'll do it when Kevin's here. Yeah, we'd be better Then the next piece was I proposed this was a an idea. I had just today Topics that we might consider for just highlight interesting things that are happening in documentation The November newsletter, thank you very much Bruno You're welcome. I also submitted a proposal as a poll request to change election rules for board board members The idea of things a discussion. Yeah, go ahead. No, no, that's that's oh, yes, and Discussion in Jenkins in the developers mailing list Then there was a new change that with the release of two dot three seventy five dot one That means two dot three sixty one dot four the preceding end LTS is now Second to life is is is penultimate, right? It's second to last and That means it becomes a recommended version for choosing your your Jenkins baseline and therefore there are changes in the documentation to do that and Changes are ongoing changes are ongoing in the in the Jenkins development tool chain to make two dot three sixty one dot four default Or two dot three sixty one dot X and what that means is Java 11. I see and Regarding the documentation it has to be Made by the human being the modifications or can it be scripted with update plea or whatever or Does it even make sense to have a robot? Change that in the documentation. Do we have absolutely to get it reviewed by a human being and no actually our robot Already does a significant portion of it and let's let's look at the portion the robot does Because I think what the robot does is actually really really a great idea that I think Daniel Beck started this idea But let's let's look at what the robot does so choosing Choosing a Jenkins baseline Here we go choosing a Jenkins version to build against So what we see here is currently recommended versions and what it suggests is two dot three forty six dot three and two dot three sixty one dot four make good core dependencies and Then here it inserts the value two dot three sixty one dot four in the recommended code in the In the set of code Well the way it computes those if I click this improve this page It'll take me to the to the the page and then when I look for Jenkins version Let's keep the placeholder. Okay Yeah, oh there it is. Yes, exactly placeholder recent LTS point high and The build process that constructs the website will replace that placeholder text with the actual value extracted from the Jenkins update center, okay, perfect and It's it's things like this one has the same behavior Placeholder latest split each of these is provided by this tooling That I believe Daniel wrote that reads the Jenkins updates and or read some other location Gets these numbers and provides them as text strings. Oh, so there is no GitHub action or whatever When those website is built it gets correct version number from another website Exactly, right, so it's it's just as just as the change logs are data-driven Change logs are data-driven from a data file that provides the definition in this case These numbers are data-driven, but they're taken from data that's downloaded from an external from another URL And then that data is fed into the process. I see so Nice nice result. That's all that I had anything else from you Bruno Regarding documentation. No, thank you. All right, then I propose let's call today's session done