 Hello everyone welcome to the arrogant upon planning meeting We are mid-December So we are going to be doing a small and a quick status, so Do you see my screen? Yes, you have mainly on the call and myself And so last week not a lot of work Actually, no work from my side That was that nice thing. I think the week before already, but last week was cancelled at the last time So that maybe it's it was still there. I really want to get to that one because it's a nice external contributor Same thing again from Charan beer. I think so if we look at that one, it's really one that actually also is really generating a lot of Noise I would say logs on century side because that's one of the thing You may remember about that one many don't know the one that shows up at startup about changing the default values for Workspace and basically what was what this thing was about? Well, the titles should be enough But yeah, it should be should be a warning when it when you are starting basically a Jenkins home fresh which is the case for evergreen setups and Because of how it's developed and how I've done it actually in the past when I added that feature It's always showing a warning even if it's starting fresh, which is kind of a Yeah misleading for users. So thanks a lot. If you're watching Charan beer because it's here here, but if we're looking here, you see here. It does the name on github That's why I was remembering that I will definitely have a look at that And I'm very sorry for having delayed the review on that one so long because it's been there for like now three weeks I think I think I linked it there. So yeah It was filed there nine of the number then I put he gave some review 20 days ago already and then I didn't manage to get back to it. Unfortunately a lot of things in my side since Yeah, I need to get back to it basically Sorry about that. And so yeah, great There's a few things there. I think last week or Louis before Oleg said it would be Making sure the right tags are there or closing or moving but I don't think I think it was very busy on the Java 11 story We are also working on a site from Evergreen initiative. So working making Jenkins work on Jenkins on Java 11 so I guess that's why he didn't clarify those things and I think that's it. We don't see here, but I because I think it was probably closed that nice thing it was so Jenkins was Evergreen Jen 5 It was this and I think by the way, I need to go and answer so that one was a nice one tackled by Jen. I Think that's her name And say well supposedly her but I can't say for sure and That's the one. I think we need to provide some feedback here Maybe either I could I should do that But many if you have a few minutes, I think you you work not part so you might or so be knowing a lot of things about that side But yeah, that's if you need to we need to provide feedbacks that Jen can move forward Hi guys Hello, Oleg. How I was talking about him and into the broadcast But apparently you have started the Java 11 preview availability meetup broadcast Yeah, I'm working right now with Whomever has access to Twitter to get it Announced that it's not the broadcast, but if anybody's looking at this broadcast Sorry for the confusion Yeah Sorry, I've been screwing up like three times in two weeks now. So yeah, sorry So let's just we were about to be to be shut down. So I'm going to just or so Yeah, so you can just continue and yeah, we all clean up for the rest. Yeah, sorry Oh my god. And so yeah, just about that while you hear Oleg I think we were discussing that just a few seconds ago and so Yeah, I think last or two weeks ago you said that probably there was a few things that actually shouldn't be showing up here or Maybe some things should be closed or something. So yeah, can you give us kind of a status update here? Yeah, just second It's basically the evergreen board so that means that there probably this there's like an evergreen label or something on those things That's why they're showing up here. Yeah, so Technically if you see some issues you can remove them Create That's a part of running PCT as a part of Jenkins core build. Yeah, it's fixed We have created all the tooling together with Raul. Yeah, I don't know why there's the label evergreen Maybe I don't know if he were you who had that but basically so you saying that we should removing that or something Well Originally, I'm always pulling has been created for Jenkins evergreen when it was Jenkins essentials Yeah, this is why the tool link is called essentials test, right? I'm not sure what is the current plan of the evergreen Subproject, but yeah, this is how we originally started the tooling. Yeah, they're absolutely though. So yeah, these types I mean, yeah, they're definitely make sense is there there's no Planning about that, but there's definitely plans. I see if there's just like slightly difference slight difference so we definitely plan at some point and overall constantly grow the Stess automated testing story. So adding PCT and ATH is In the standard evergreen pipeline is definitely something we will at some point reach But right now it's not the case yet But yeah, so it definitely is something we will want to do at some point So well, I guess I'm going to keep that for now on the board because at some point we see if we want to say Okay, this is an epic or whatever and we repurpose that thing for you know doing that also on evergreen side or whatever But yeah to remember about that and then I will close it or something if I file a new one basically Right and so the other ones. I'm not sure they were also relating in the end to evergreen, but I guess it's kind of the same story So So artifact manager S3 can be closed we have all the flows published Remote and Jenkins integration test. Yeah, we need to keep that Yep, yep So, yeah, I guess we keep everything and I will clarify after the protocol anyway So thanks everyone. I want to just stop the stop the recording and clean up my my screw up