 Yeah, so hi everybody. Let's start for this new info meeting We don't have specific topics that we have to discuss today. So we just did I Would just start a quick overview. So the first thing is the so as last last week I mentioned that we had some issues with the fastly accounts. So I created on the fastly accounts I was supposed to be granted with a specific open source arm I was supposed to join the open source program and we had some issues and it should be solved now. So Either today or tomorrow should start configuring Fastly to use I mean to use the CDN for checking that I also did something that should be coming in the coming days Otherwise the main topic has been to work on the check ins release automation projects So we did a lot of Testing around the packages that we are generating we spotted a few bugs and and we fix those bugs Now we are mainly working on the documentation. So I sent an email on the mailing list one hour ago asking for feedback if people are interested to I mean Just asking for more fees for more feedbacks and otherwise we should try to Plan a release probably next week Depending on how the coming days is happening So, yeah, do you have any question now? Do you want to bring any specific topic? So the thing is the do yeah, yeah, I liked I liked all like suggestions should we already consider? We were delayed this week on doing the weekly. I assume all like that the weekly has not yet happened even now and Thus is this is an excuse to say let's test drive the this with the current weekly Yeah, we can do that So basically somebody just needs to paint KK and say that whatever you were doing is don't I Haven't sent a message yet, but if you have an opportunity why not there is nothing really critical in this release Well, yeah, I like I like that approach because it lets us do it during a weekday Without feeling obligated to do it Sunday night to match with something that had been done previously So it's a great excuse to try it Actually, we do it on Monday. Even if we weren't to do it this week, we'd do it on the Monday wouldn't we just so that it's not in the weekend Agreed agreed in the future, but yeah, that's valid point So, yeah, my my only concern to do it right now is that there is one last Bugs that I would like to solve so basically right now we are generating index that HTML So basically many cover package the Jenkins that I own So when we generate the artifact we publish that are those artifacts and then we generate a website With information like how to install they beyond how to install read that and son and there is still a last last But I would like to fix on that part So it does not really impact the release process or the packages that we are generating but more like When we generate new release we also publish We also update the package website So I'm I'm much less worried about that than I am about the things that I think we don't yet know about But we will learn about by the virtue of running through the process The package page. I suspect there are many many more things that we haven't yet discovered that are that are That need need further attention Okay So otherwise, yeah, we can we can start so what like what would be your when would you like to start this tomorrow? Well for me, I would prefer to do it tomorrow on Thursday so that we have some time to react Basically, I can just Dedicate almost all the time I can send heads up to KK But the Team is here. Alex is here Marcus here. So basically all core maintainers around Except Oliver, but for Oliver, it's less of concern at the moment until we ship LCS So I would give it a try in the worst case we botched as a weekly release We send a message to KK asking to Ship a new release on the top of that Okay, not something unknown It sounds like your plan and for me for the things that I want to push I only want one only only one or two a word to implement that so It should be ready for for Thursday. Well, so could we I have integrated KK release a few minutes ago. Oh, okay done even better. This still gives us an excuse We could release a new weekly and and just admit it's a discard. Couldn't we? Yes, yes, you have a lot of things in the backlog And then the pull request keel so creating can save release for tomorrow or Thursday still doable sure Maybe even a mock release without changes, but we definitely can integrate something There's one that's ready with the two line documentation change and core maintainer guys Oh and the maintainer guide. Yes, there you go. Get that one merged. Yes Well, these changes and user facing I would prefer to lend something small but user facing to be honest, okay Yeah, that's for sure and I still have a plan to propose one line fix for Jenkins for the runner So yeah, I can just submit it Okay, just to read global configuration if Daniel would reply or even Felix's time stamp for the thing we could go in Yeah, so yeah, we can take it offline but So Oliver So Olivia, what's your preference about the time when you would like to ship it? So for me, we can we can plan Thursday seems to be a good time Let's say, let's say, but I mean, let's say the time where we have people on the US and people in the Europe leg three or four PM UTC maybe three PM UTC Let's let's see the best time, but I can send an invite for Thursday to the people involved Yeah, that's right. We also need to send heads up to the developer man at least just in case So If you could do that, it would be great and on our side, we will prepare some changes in the master branch tomorrow Just a quick reminder on the time here on the timing here triggering a release the release job take around one hour 30 And the packaging job take around 30 minutes in the 30 minutes have 15 minutes ready to generate the packages You have 15 minutes to generate the packages and you have 15 minutes used to synchronize the different doors Should we trigger the release earlier? Is that the real there the release doesn't really matter so much It's just release is just what we're building if you just trigger it around lunchtime as long as we merge before then And then it's the actual essential packaging and deploying the artifacts that matters Well, and and don't don't be hesitant to do it earlier in your day Olivier because Alex and I are both though. We're in the US time zone. We are certainly Early risers and on Thursday morning will be up very at least I'll be up very early Markey, I don't know for you But but I think you should feel free to do it anytime on Thursday. Don't don't delay till your afternoon agreed Agreed Just quick check before I go to the credentials. I just want to be sure. Um, so a leg has the permission to To to push to Jenkins here slash Jenkins and the master branch if I'm right No Well, I think they have never requested these permissions. So because basically I will have some in the current process I will have so let me open the variables I mean, you need a right key to Jenkins to Jenkins repository rights. Yes Yep, so I need I need I need to be able to write the chat in CS Alex and Alex's access to do that. Yeah, I have access on the org So I also need Right permission on the Maven repository. I Don't have access to do our factory stuff Is it only a Daniel I think that might be Daniel Well, technically we could grant access to someone but only yeah, I think it would be better that Since you have flux to the process that you could just orchestrate it and if you need permissions To push to the code, I think we can grant them by Thursday Yeah, so I just Um, so Jenkins here, so Jenkins are factory and I think that's it Yep, that's it Um, so yeah, okay That yeah, that's on that sounds like a grid plan. I'm really happy to test this There is also another topic where marky whether he's helping his Auditing the the community's cluster and see how we can improve the security process I don't know if you have any update that you want to do here Marky I ran. Yeah, I ran the initial scan Uh, and it didn't break anything because nobody said anything. So that's a positive Uh, I ran that. Uh, I need to configure the scan again To run what I want to do on the second I want to see if it gave me the same results back that way. I know It's actually running correctly Uh, and then I will run finally before next Informating I'll run a third scan And then I'll publish the results. Uh, when I publish the results. I won't make those public I'll publish them in a spreadsheet that I will uh, I'll share it with everybody on this call Okay, which tool are you using for the scan? sonar boy Sonar boy Yeah, okay So it was it was a tool designed by heptio and now they're under vmware, but that's pretty I I looked at spotifies cube cube cube bought it and I they did the reason that I did not like that tool is it required too many permissions Uh, and and instead of adding the permission separately It altered existing permissions and I did not like that because I did not want to have to go back in and change Uh, those cluster admin permissions in the rbap Okay, thanks Thanks for that on this. Um, yeah, thanks um There is any other questions or topic on the automated release So I don't know if you already started thinking about how we Planned to release as well the stable release or is it still too early to discuss about that? So let's just focus on the weekly Focus on weekly for me. Yeah I expect I expect several surprises on this one and several more surprises next week And we're going to proudly by the end of april say we got it. All right Okay, I just I just want to be sure that it's still in our head So if we have to to implement a fix, um, it does not impact the way we would release the stable releases So that's the only thing um Otherwise Sorry They have network issues didn't meant to interrupt you I just wanted to ask whether you want to establish some communication channels for jankin score for thursday It looks like it would be a good thing to have them When we do all these releases And yeah, there is ongoing hollywood about slug versus gitter versus matrix versus whatever But maybe we could make an intermediate decision how we communicate during this release To me to me to me do the most important one is the jankin's Uh mailing list the jankin's dev mailing list, right? Well, but I thought yeah, I thought you were I thought oleg was targeting High interaction communications Back and forth not not not informational Oleg did I understand you? Yeah, that's totally right. For example, we had the same kiss with alexo and team With regards to docker agent renaming Docker gitter So it was also quite a runtime communication And if we end up with needing something like that for jankin score, I would rather prefer to have a channel for that Okay, so now the question is My assumption was we would use irc because that's what we've done before with jankin's infra Um, I don't find That's my assumption as well Yeah, that's my assumption as well and all the people involved in this can use irc anyway, so Okay, then I've seen this Well, so oleg were you were you considering? Hey, should we try something to try another channel for me? I like irc right now because it's familiar and while we're doing something that will be new and somewhat unfamiliar Using a familiar channel felt like a healthy thing to do So the question is which what new tool do you want to bring in the loop? And I in this case, I don't I want to stay with the old tool personally Just just so that I don't have to worry about tool changes and Build changes we can change tools later a week or two from now I agree with that sentiment. I agree with mark sentiment. I definitely think there should be a discussion about the tool change But I don't think it should happen in conjunction with the release Okay, so let's stick to rc for now um Yeah, otherwise If we don't have any other puppy that we want in this case, I think we can stop the meeting here I just had one thing that would be good to get fixed Incrementals has been broken for a few weeks um With the I think the passwords expired, but I'm assuming that you don't have access currently to fix that, Olivia When you say Tim when you say incrementals broken incrementals for jankin's core incrementals for Everything incrementals publisher Oh It gets a great So the credit the credit card is to a full artifact area, right? Yeah Yeah, that's the artifact or credentials looks it looks like it's the artifact or credential Um, would you have the logs that you can that you could share? I mean it gets a 403 When I try to publish it gets a 403 I believe Yeah, then then I can contact Daniel to see um, yeah, if you if you can share as many information that would be useful But otherwise There's at least two tickets open. I'm trying to find it So that that would be a help for me as well I actually have a pull request to a certain plugin I maintain that needs an incremental from another plugin So I didn't realize it was broken and I awkwardly suggested that the student suggesting it should use incrementals And so now I've lied to the student. Sorry about that. Yeah, it's getting a green tick But it's because it's It's ignoring it's ignoring errors just like it should except that we're ignoring the error like we shouldn't got it Yeah Here it is his chest to Jesse raised this one It's an ISE now Can you share the the ticket either on rc or in the document? It's an ISE I mean Yeah, so I can see I can see the function, but I can't see the logs to the function. We nice to sort that um, okay, so, you know just One last question before we wind up this call. Um, is there a person interested to participate in the fastly configuration? Do I mean is there someone who want to have access to the account? Because right now it's only it's only because you can't me I'd be interested in helping out Okay, so I can send you an invite I had one quick item if if there's nothing else Yep So we're gonna have um s390x and power pc and arm Agents coming up. Um, our labeling right now for like docker jobs is just the docker and label So we need to come up with some labeling mechanism whether we want to Change things that currently just require docker To require docker and something else Or mark doesn't like that idea But we need some way of Labeling things so that we don't put the wrong jobs on the wrong Or the job the right job on the wrong agent Within the infrastructure. So just something to think about Okay, um, I don't know if you had the time to because I did not follow anything regarding the work there But regarding the iB infrastructure the adding those as agent and Seattle Jenkins that I own and and some was the current status there Because as far as I know we still have to We still have we still have some script to configure those those infrastructure And then we still have to add those machines to Seattle Jenkins that I you're right Yeah, that's correct. Currently. We do have arm You you added the um packer imaging for arm on aws at least so we have that and that is docker capable um, so We can't label it as just docker So do we do we want to start doing arm docker? You know s390 docker as one label that just Then we can talk about an irc. I just wanted to get people thinking about it Isn't there is there a platform label at plugin that does this for you There is but I'm not sure that yeah, there is and we could consider that I'll bring it to irc and we can have a conversation There's also an implied labels Um, there's an implied labels plugin that will use apply rules to existing labels to generate new labels for us So we could we could talk about both those I just know that there are a ton of uh Things in like the pipeline library that look for just docker as a label Right, and I like that so that's why I think we should not docker really implies amd64 and Exactly and we should just admit that that's the reality. We're never going to be able to change that whether we like it or not Yeah, but so but for these special ones They just need some other label or some suffix or something Yeah, even the best way to do that because we'll need it for doc We've got something like that with wind doc right now, right right alex So so we just need to choose a scheme that will work for us dealing with Multiple platforms and not breaking the compatibility. We have the existing labels. Yeah Okay, so let's continue this discussion on our team. Um, thanks for your time and see you later. Bye. Bye Thanks Cheers everybody Thanks