 Hello, I think the you're getting key the Oracle guys told me that they have some big meeting today So they won't be able to most likely join Maybe Hey, you're again did but I assumed also since they're kind of together the both would be in the meeting. I don't know Hey, man. Oh, can you hear me? Clear good. I think with the microphone you have you can hear you from from the moon Dad microphone again Yeah, we have a friend that really enjoys my microphone. This will be small round today. Where is Lewis, man? Okay, um, let's start Or call we did community questions Okay, then let's discuss the release plan. So 0.5 branch was created. Thanks and So, do you may you put this in the for the agenda is this the only two PRs that we want to get in before we do 0.5 Yeah, I think so. I mean those are the only two ones we have opened and and Yeah, yeah, that's right issues of PRs This maybe with the retry Definitions going in Do you think we should make this attempt of putting our handling in a separate section? Yeah, that's one of the PRs that are just of those two that I put in is the bigger air handling PR and We working on it and talk to your again and We talked about it all pretty much all day today a couple times and then we got I got a good idea of what He would like to see and I think he makes a lot of sense. So Again for like the fourth time I'm rewriting the I mean not rewriting but changing because he involves a bunch of examples and stuff like that So it's every time you change something. It's a big deal but yeah That's the big one that I'd like to push in if the other one makes it in for 0.5 or not it's kind of like Okay, my opinion, but since it's already done And I was hoping will it would be here to to because last week we we wanted to ask him some questions So if that one gets in I you know, it's fine if not It would be nice if we did and then all the issues that have to deal with retries I talked to it because you're gonna open them all he agreed that It would be okay to do impose 0.5 as additions Because even with the retry definitions as we have and now you can define retries very well It's just his would be enhancements to that for the next version. That's the exponential back offs, right? Yeah, cool. I think technically we could Check on these PRs and just decide to have them in right Still with the condition ordering I have my doubts because it is part of the format there is ordering and even if we had priorities It's we'd have to clarify how equal priorities would be handled and then eventually they go in by order How they appear so I wanted to learn more about the use case if it was that multiple conditions might be merged somehow, maybe there is an IDE that wants to Do this and then of course priorities they do make sense because You wouldn't know in what order to merge them to begin with But other than that I I can only see the that it's already part of the language ordering And it's ordered arrays are both or lists are ordered both in yaml and jason That's my concern here. But if you think otherwise, then let's merge it Now we can wait on this one. I am not opposed to it Waiting yeah, let me actually do an AI because I forgot to do that last week Dr. What is it Lewis with the oh or are you yeah, Lucas Lucas But um, yeah I'm honestly fine with this going into after release, but the area handling we got to push that in I just It's just the parent is not done yet I like to need one more hour and then I'll think everybody for review again, please if you can do it this week I would really appreciate it. So over a weekend we can do the tag Okay Pending changes and What are you called that offline review or reviews, okay, and then we can push that in and Then we'd be done for this zero point five or so part of this is Is this separation of error handling in a new section or? No, the air handling right now is it's defined in our specification It's pretty garbage honestly, and it's a section that we've improved everything except that so this really kind of steps it up a lot It's a big improvement and it's something then later on we can work on to adding like the retry stuff that you know Your gun is looking into So he reviewed it already this morning. He said he couldn't make the Reviews and and based on that I I still have to make a couple more changes But basically what it is is We're gonna do explicit the air handling You can take a look at that we're on errors. He's going to define an explicit name and a code of an arrow Here and then retries are going to become a top level definition like events and functions Because for me try definition and it makes sense if you want to externalize it or if you want to have all Timeout errors in all states to be handled similarly or in the same way and then on errors Error definitions you can either reference a retry definition, which means you want to retry or If you don't that means you just want to basically Catch that error and transition or end workflow. So it's kind of like Yeah, so it was good to me Simplifies things and yeah, I don't want to talk about it. Just review it whenever it's done. I think Okay, let's peek at the issues so that closes I think the retry definition No, sorry before that. Oh, we had this very old one update where workflow handling Max attempts so this retry definition section the general section Do we want to do that after merging the PR? Yeah Okay, let's let's get do this one PR after another because they are so related and Then exponential back off goes in after 0.5 Uniqueness constraint for workflows You happen to know what this is about. I think we pushed this out. We out. We didn't have time to talk about it This is a correlation. I thought in general we was the correlation token. We're good Yeah, this is we do define correlation between events But this is correlation between Workflow instance data and it's a lot bigger thing to think about so it's that I don't okay So if it's cross workflows, then I think There was also to be pushed out and Then the Jason patch schema are Ricardo since we have you Do you want to do anything with this before 0.5 or oh, no, no, no, no, I believe that we can we can we can push that Just check in for the release. No, no problem. Yeah Okay That sounds very good and You don't mind Short call then we can close early today Let me check any other business. I think we Just would like to share about the As the go SDK We finished the most most of the work on the on the SDK side So now you can parse any Yemo or Jason file and from and go Types and This is basically on the first feature that we'd like to to have On the SDK, so you're pretty good shape for a cube call There's a small roadmap that I shared as well in the wreck and the read me file So you can take a look on that to see what is planned for for the SDK So it is basically for now I'm planning to you know, align the features that we have on the Java SDK with the goal is because it is basically the same thing for now like being being able to Create a workflow using a fluent API or generate an SVG Image from the from from from the workflow definition But the the hard work, you know the two parts any any file any more Jason fine into go types that's was the What we needed actually for the go SDK because we had hadn't had on the time or the actual feature in the old let's say SDK because in that oldest cave we will we would have just the The types defined based on the schema so that was wasn't the work too much But now you can you can actually use the SDK into your application or Go app or whatever Is that based on the Jason spec? Yeah, it is we generate code based on the on the Jesus pack Let me ask about code Or the completeness of this Jason spec code generation because I found that different generation code generation tools Yeah, they do different jobs on on this schema generation if it's just a schema I mean that that's one thing but does it account for the the rules that we have of whether elements can appear or not whether they are optional mandatory and Yeah, they follow the So some some of the spec The workflow definition validation. We don't have it yet. It is on the on the roadmap to take a look But for instance a goal doesn't doesn't work with interface like Java so for instance today states attribute and give a lot of pain to implement that and we had to write a lot of Custom code to encode from Jason, you know, and just to figure out what kind of data or what kind of state There is expected to be in there like an operation state or switch state Because you don't have interfaces and in Jason are in go. So You know in the way that we have On Java for instance So, yeah, it is working pretty, you know good for the way you have And it's more validation. Yeah, we we we also have as well So he thinks there is no polymorphism of the structures used, right? Yeah Okay, cool. I also had Any other business and that is? How do we go about the release? So when we freeze it now and we only have This week to make it public because there is already KubeCon next week. What is it that we want to do? Any ideas Very welcome. So sure everybody personally can tweet about it Put it out on on LinkedIn share as much as possible. I think there is a cncf The project support service for a newsletter entry Something like that Should we ask about this as well? Yeah, I think if they can help us ever. Yeah, definitely Probably have to put together a small text for them describe a little bit what it is about the release and Yeah, I mean, yeah, but look Roadmap and It's a lot of things. So maybe we could just pick like a couple of the big stuff that we've changed since Over the year But yeah, I mean we yeah, definitely we could use some Yeah, like Twitter and Maybe I don't know what else can we do? The problem is we already recorded the videos for KubeCon. So we can't really add that to the videos now that kind of sucks, but Anya, yeah, maybe Karina has some ideas. I don't know So, yeah, I was thinking of including some some tweets and posts on a couple of our Community stuff for Red Hat projects. I don't have any account right now for the serverless workflow And also it would require building it up a little bit before we could actually gather results from it like from a from a serverless workflow Twitter account for example, we won't have that much followers right now But I think that's that's how we should go. That's what I think we we could do right now because that I mean most of the The people we want to reach are actually on Twitter and LinkedIn I don't think that Facebook is a good strategy right now or Instagram for example Yes, there are a couple of Online sites for blog posts, but Require work for example mediums or That is true That is true. The problem is that we post Posting the same content in different sites can make this car go lower and people won't find out about the blog so much Like it's not displayed as much as a post that is not Reposted in everywhere. So if we would like to have something posted We would need to create different texts to put in the different blogs or just go for one of the blogs So just a note here Yeah, and I have a really good blog that we worked on for Recently I can just share that with everybody you can reuse it. Maybe change some words in it Yeah, I can get that out on these Anything else we can always spam the serverless working group mailing list And possibly Yeah, we can't blog on the NCF website. I was told that the only incubating projects in higher can do that Okay Do you know about the newsletter? This media relations How about this sick, I don't know which sick we belong to It's still application delivery, isn't it? I have no idea honestly There was some talk that Doug's team would become a sick. I don't know what happened with that. I'm kind of out of the loop completely Yeah, it does matter Whatever works like anything is better than nothing and that's kind of like the approach I Would also Karina I would like to maybe if we can at some point, I know I'm pushing all the work Like create a YouTube channel because I'm starting I have like three current videos and I will create more like every other week hopefully and I rather not post them on my YouTube channel, but if we had our Team one, I think that is pretty a great idea actually I can do that for us and Share the the access with you So if you want access like admin access any of you, just let me know which is your YouTube email your Google email and Just please send me the logo that you have so that I can use there in the YouTube Yeah, that's not urgent like don't like if we talk about something here It's not like oh, we need it by yesterday now. This is free time work, you know, so don't put it on your schedule Thanks Okay, and the timing I guess should be Yeah, maybe it's still early enough at our next community call. All right, that's right before cube con What do you think people's channels will be? congested with cube con stuff What do you think is the good timing? for this I Would publish it before Cube con I would also the recording was already done So it doesn't matter because I mean we could just put it there upload the videos that you home You already have to the channel and once people saw it Maybe they could subscribe because they would already know about it So the best time it would be before the conference But only if the guys have a way to share it somehow maybe on the chat I don't know so on slack and of course during our presentation or after our presentations there's always the Q&A and Maybe it can be put out as a Last comment just before the Q&A finishes. All right Last time we my presentation was the serverless practitioner summit and I was Not a lot going on during the Q&A. I think we had two or three questions This time it will be on the main conference, but I don't know if that's More busy if not, I I can I gladly give a hint anyhow, I have a hint in my presentation to serverless workflow and Possibly also to the office hours. I'm not sure I put that in and maybe I just mentioned the website Yeah Okay, that's cool. And of course There is no serverless practitioner summit this time, right? There is a serverless channel, sorry Interrupting you for next group come let's do a release a month in advance man because what's happening is right now Also the project booth that we have not number one thing. I want to say we should be happy with what we have this coupon We got two or three two talks specific about our project. We got my nose talk You're mentioning in it. We got two project office hours again and a project booth So we should like be happy what we have. This is just like cake on top, you know, or whatever However, the same is so yeah, whatever extra thing this release if we have time for it or not everybody's busy I'm happy what we have but in our project booths. I mean project office hours. We can mention the release the project booth Unfortunately, it's locked. So I can't add that anymore in there. So what it is? It is what it is. You know, oh That's locked already Yeah, oh Review they have to review it for every project apparently so they locked it up for me at least I can't make changes Okay. Yeah, so then back to timing this week would actually be better, right as soon as we have version Well, I mean It all depends on some people. We need like I will we need to finish this PR. So reviewers are needed I'll do it in an hour. So That's step one. Step two is Ricardo and I need to fix the SDKs One thing we need to figure out What we kind of heard what we gonna name it the version and don't worry the version does not have to be 0.5 the SDKs Have convert a name distinct whatever they want most likely of 0.5 But whatever then we also need a release of the visual code plug into the Microsoft VS code marketplace. That's not a problem. I'll deal with that So it is I mean it's not and then we also have to The easy part is just create a tag and then tag the 0.5 X branch and The last thing that needs to be done is there's gonna be a PR on master to update the latest version links You know on the read me on the main read me there is a link to latest release and current mass whatever And we should probably also not call it master but in the future we need to rename that you know whole Language thing. What is it called right now? Is it Google changed all this stuff to main, right main? Yeah We should probably do that at some point as well Before CNC FS goes to do it Wow, I haven't noticed that yet. Okay, so main and Is then there is there a development branch? Oh His main is is that to develop a bunch? Well, I think the way it works. We just renamed master to main and push it and But I I've never done it that I'm scared of breaking stuff and Don't worry, I won't be I want to be that that hard I've did that already on all the projects in the community that I that I'm that I maintain and Was pretty straightforward. It's just a pain, you know to change the the local links, but it is okay to do that Actually, there is a list of words that we should avoid I'm not sure. Where is this list? I can I can I can take a look and I I can you know share with you to America's it is not just master it is You know a black list white list slave all those words that we should avoid and We need to just search through the the report storage of this to see if there is any mention Of these same things and then we should you know, they extra care when we are you know rephrasing our dog documentation or not creating sentences and then things like that To be gained their why gender wise and all those kind of stuff Ricardo this air air PR will The Jason scheme us a lot So yeah, in addition to just what when this air PR goes in air handling PR We need to before also push it in into the SD case Yes, for sure Okay, that's all Okay, then I think we can't have an hour that we can make a lot of use of Thanks, everybody and Read you soon, I think we yeah, I'll be waiting actively for the for the PR to me to review I'll take extra care that this email doesn't slip my mailbox No problem. I'll ping everybody in the Thanks Thanks, man. Oh Goodbye. Thanks. Bye. Bye