 Okay, we should be live on YouTube right now, so be careful what you say Yeah, hello everyone Last week I will that last week two weeks ago. I was alone today. There is more of us At the meeting and we don't have a huge Long agenda. I'm gonna share the screen so you can actually see it my entire screen and And then of course I'm showing you my company slack perfect So I hope you can see Jcast office hours minutes of meeting document in Google Docs and Yeah, so we have Me John and team I Hope that's that's how you spell your name Very good. And there is a couple of well things I want to point out or mention and John and team whatever you want to add we can add it. So let's start with this Pull request by Joseph To help us clean the issues We have a number of issues and some of them are well not Important anymore or doesn't make said they don't make sense anymore or we just Didn't give them enough attention and some of them are not worth keeping but it's it's not that easy to clean them. So Joseph had an idea to introduce this stale manager and Clean the inactive issues those inactive issues and full requests and he proposed the Solution so Yeah, I actually did something so we're waiting for that to be merged but I Had a look at that and I I'm actually happy with with his proposal and team also accepted So probably it's gonna be merged very soon So if the issue the will is inactive for at least 90 days It's gonna be stale and we have some labels that we can use to prevent the issue from going into stale and And of course if the issue is marked as stale and You're the author of the issue or interested in the issue for whatever reason just just comment or Or act in some way. Let us know that that this issue Should not be removed. So so it's not like we kill the issues and they are gone. It's just to help us Clean the stuff that is well, not not active not valid anymore and Yeah, no one was complaining about it. So as I said, it's gonna be merged pretty soon team Do you have anything to add regarding that one? No, other than that we use it at work Most of the time when someone when it goes stale, you normally see activity either someone closes it straight away Or they remember about it and they just forgotten so either way it's always been useful for us Yeah So just just like for yeah for everyone who's who's using it It's not like we we like we don't care about the issues and well, we just closed them. It's it's just some help to Not keep them open forever without the reason we can always discuss each specific issue. There is a problem so, yeah, I'm not sure what What Joseph is doing with it now, but It should be it should be pretty close to to being merged and then we have this idea to Targeting 2.164 dot one For jcask and I actually have a question Regarding that one and it might be pretty dumb question that will reveal that I have no idea what I'm doing But if we switch to 2.164 dot one Does it mean that from the version of jcask that will be targeting that one you can only use it with At least that version of Jenkins or or Okay, but I Mean I'm still I still think that The issue makes this poor request makes a lot of sense and then team you commented that it might be best to wait for A couple of weeks to get the numbers and Yeah, yeah, so that LTS was only released like a couple weeks ago and the We it wasn't out when the statistics were last published So at least we until the next statistics are published Now April so there should be there should be up. So we can have they might be up now. They are up now with this I think yeah, too. Yeah, they've updated the statistics to include two one six six so They don't use the sub versions of was it one six four? LTS is probably released after that point. Okay. Yeah, so there needs to be Yeah, so we need to wait for the couple weeks to stay one six six was 26th of April Yeah, okay Yeah, let's market pins. It doesn't get stale How do you market peanuts just a label? Yeah, yes Very good. Okay. So everyone agrees we want to move With the with the Jenkins version and we'll wait a little bit to like make that Change be yeah makes sense And that's that's those are two issues or poor request actually I wanted to talk about and We have a lot of poor requests that are either working pro work in progress or needs to be retriggered so so the Teek is green and we can have a look at them But is there anything any any of you team and John wanted to Bring out up today Okay, it's nice to hear you But I'm not I'm not gonna keep you much longer if there is if there's nothing else to discuss right now I will I will poke the PR PRs authors to to retrigger or make sure there there are no merge conflicts Especially with the older PR so we can also clean the PRs without losing anything important So let's hope we will have a little bit more to talk about Two weeks and in two weeks. I'll be in a train. Ah, yeah, but it's not gonna be Wednesday. Sorry it We should have a meeting again in two weeks sure the link to the Calendar Jenkins calendar where could you kind of repost it because I've thrown it away somehow Of course, I will I will I will put it on Victor How about the how about in our the office hours minutes of meeting blink there? Sorry, you want to put the link? Yeah, the link in the office hours because I was thinking that Gitter you blink twice and the message is gone A lot of stuff is going on Yeah so I'll put it and I may even put it in uh, or do we have it somewhere in read me in uh Couldn't find it. I couldn't find it in the read me. So Oh, pull a new pull request update read me Yeah, there's gonna be one Okay, so I'm gonna I'm gonna make sure that Link to the calendar is available in wherever it can be available and um, yeah, I guess we're gonna close the meeting All right, thanks. Thanks for joining