 Hey, can you hear me? Yes. Yes. Awesome. I can one second to log in and to show the document. Can you see the screen? Yes. Yes. All right. So welcome everyone to the Hyperledger Cacti. Please abide by the anti-trust policy that I'm showing on the screen. And also the Hyperledger Code of Conduct, which you can find linked to on the agenda document. And then I just created the agenda document a few minutes ago. Sorry about the last minute nature of that. I have one thing, which is just to say that I started cutting that 2.00 alpha PR for the release that will bump up the TypeScript packages as well. And then I'm going to work with Sandy to make it happen. And I don't know exactly how we're going to do it with the Go modules yet, but we'll just, it's going to be scrappy and they'll just discover what the issues are. And then fix them. So there may be mistakes because I just don't want to overanalyze it. I don't want to, I don't want us to spend a bunch of time trying to make it perfectly first time. I'm just going in knowing, oh, it's okay. This release is kind of going to be messed up. Maybe the git hashes will be out of sync. Some other mistake will be made or the NPM package publishing will be broken, whatever. We just going to do it so that we see what's happening. Thanks. So the, I guess the current PR has not been approved yet, right? Sorry, what was that? The PR is not being what? The latest PR, Sandy PR has not been approved yet, right? That's approved. That's merged. Okay. So yeah, I was about to say I thought I proved it. Sorry if I didn't. Okay. No, sorry. I didn't check last night. So packages have been published. Is that Sandy Purdue? No. So that's what I was asking on the discord with whether I should create a release, like a sample release or test to those workflows before the actual release. Yeah. Yeah. Cause when I go through those release steps that we have in the release management document that I'm going to show in a second, just so we're on the same page. Shoot, where is it? What? Why is this not? Oh, because it's still in the porous. Sorry. Yes. Yeah. So this file has the steps that I'm going to go through. And I'm going to do this just replace everything with two zero zero alpha one, something like that. So I'll do all this and this is ending with the tagging where I do the get tag and then I pushed that to the main branch. Okay. Sorry. Yeah. Now the font is bigger. Yeah. So this is the crucial step. And then that will trigger the. Sorry. I'm blanking the workflows. Sandeep's workflows. And, you know, if you get lucky, all of those workflows will just work and it will be great. Everyone will be happy. But honestly, I kind of expect a bunch of things to just fail. And then we just go back and issue later on, you know, later this week or next week early on, an alpha two release, see if it works. If it's not, we just hammer it out until it does. And then at least we will have the release process in a shape where it works. And then if you want to create as many releases as you want to, we can. So the idea is to release a tag. The different name from that should release that. Just for testing. Sorry, I took, I have seven trouble hearing you, Ramu. You were kind of cutting out and not very loud enough. Yes. I was going to say like I created a branch alpha hyphen pre release instead of alpha one for testing. Is that fine? Like if we can do it in that. Otherwise, otherwise I'll have to change the versions in the viewer directory. I think it's fine for now. I will call mine alpha one. And if we do it again, you can call yours alpha two and I will also call alpha two. Because just because they'll probably need more of them. I, it's very unlikely that we'll just get everything right the first time. So that's why I would put a number in there. Okay. But for now, if you did your alpha without the number, I think that's also fine. I just, I want us to be efficient. I don't want to take more of your time. We can just see how it goes. And then, you know, on to alpha two. Whenever they see the phone. Okay. Yeah. Yeah, so no worries about that. I'll just do my side of the release tonight. I mean, then we'll just see how it works. The only thing I ask from everyone here is to be on the lookout for that pull request and then just review, approve it as soon as possible. It's not going to have any code changes. It's just the usual release like changes that are basically just all two generated stuff, you know, the pumping of the versions, the change log from the commit log. So it really doesn't require that much of a review. You kind of have to say yes. But it's if the sooner you do that after I send the PR the better because then the sooner we can merge it sooner we can see what is the actual outcome of our attempt. You can do that tomorrow. No, I'll do it. Either right after the speeding if I have enough time or later tonight. I will be up late tonight because I have, I have a thing in a couple of hours from now but if I can get this done before then then then but if not then later then then three to four hours from now. Okay. Yeah, it should still be during your office hours, regardless of what happens unless something really goes bad and I just cannot figure it out but I've done I've gone through these steps a bunch of times and usually takes me 10 minutes. Okay. Is there anything else? No. Okay, I don't have anything else either this is just what I'm working on. And sorry again if I'm slower than I should be. There's just a lot of competing things parallel stuff that all demands by attention. But this is definitely one of them. That's important high on the list. Thanks for your worries. Zuru, do you have anything? Any discussion items? Nothing for me. Thanks for your work. Yeah. I'll review your request when it is ready. Okay. Cool. Then thank you everyone for joining and I'll talk to you next time. Thanks. Thanks. Bye.