Transcript for "What's New in ChangeMan ZMF 8.3.2": Good morning. Good afternoon. Good evening, everyone. Wanna welcome everyone to the what's new in change me in CMF eight three patch two, also known as eight three two. I'm Jimmy O'Rourke. I'm the product manager for ChangeMeInCMF. And with me is Bob Yates, who's our principal solutions architect for mainframe and enterprise DevOps. I'm gonna take you through the what's new for eight three two as we've done in the past. Just a little bit of a note here. Bob and I had talked about this and kinda weighed in some of the pluses and minuses for this. This is probably the first what's new webinar that we've done where we really don't have anything to demo. That doesn't mean that there wasn't any valuable enhancements being put into the release. They just really weren't good ones to actually do a demo against. And, you know, we looked at this to kinda figure out if it actually made sense to do one. Historically, we've been really good keeping up with the tradition of doing them since 08/24. So you can think about the amount of leases we've done over the past, I guess, almost five years now at this point. And, we've just been doing them, and we thought it'd be still good to do them just because they can still be informative to everyone. And, you know, quality is always better than quantity. So we might not finish, you know, the the typical sixty minutes that we usually take for these things. But, you know, if we can give you back fifteen or twenty minutes, I think it's still valuable for you. Just a little bit of housekeeping. I think by now everyone's familiar with the format that we use, which is Goldcast. We have the q and a and chat panel. Both are available. The preference is to use the q and a for any questions that you have, and myself and Bob will monitor in between each other's presentations. We also have a couple of people, behind the scenes. They're also monitoring as well. One other thing to point out is that the survey, you know, we're gonna try and keep that up for a good two minutes after the presentation, ends. And the the the survey itself has about four different questions. You can see here I have some bullets there, and they're specific around Git and Versus Code. For the customers that attended, and we had a lot of you, attend the VUG, the virtual user group back in November. There was a lot of emphasis around Git and Versus Code, specifically where your adoption is. Are you, like, now within the three months time frame? Are you three to six months, six to twelve, that kind of thing? And, the survey really helps us to see if there's a trend. So that was about four months ago now, five months ago since we did the the, the bug. And so at this point, the customers that were in the three to six month time frame, you're probably now in the now or under three months. And that's really what we're looking for. Secondly, it will also help us, you know, discover what customers would be interested or we should target for a formal beta program. We are expecting to do a beta program for Versus Code and Git, which will be the tail end of this year before we go to release. So it's really important. If you can take the time to go through the survey, it really just helps us, again, to figure out trends and what customers we wanna be able to target, for that. H v two had, 40 plus enhancements. You know, it was around ERO, d b two, rest services. We had some XML updates, admin functionality, adding change packages, and about half of that. So 20 plus were custom defined enhancements. And so we wanna thank those customers that went through the trouble of going through our idea portal and filing your enhancements. And some of them are a little bit older, some of them are a little bit newer, but we're able to get those into a three two. We've been really good since about 08/24, 08/25 when I came in and became the product manager. We've been really good about just making sure that customers are are front and center when it comes to these patch updates. It's also another reason why we switched from, you know, having an active, patch update versus a stable, patch update. And I'll talk through that a little bit more in the next next couple slides. For eight three three, couple things I wanna point out. So obviously there's gonna be we have a a good backlog, healthy backlog of zero, d b two. We have some catch up to do a client pack because you'll notice we didn't really do anything for 832 and for, some admin enhancements. But the first two, Versus Code and Git, it's really, our number one a and number one b in terms of prioritization for the rest of this year. You'll also notice that the time frame is q two. Now I highlighted this back in, during the bug, the virtual user group. So nothing's changed there. But things I just wanna point out is that we've been really good about doing these patch updates right around early part of q one, shortly after the holidays passed us, you know, right in that January, February time frame. We go and do a patch update release. In this case, we're gonna shift it by about one quarter, about three months. And the reason for that is that it's a very aggressive, timeline we have for both Versus Code and Git by the end of this year to do our first release around those two things. Secondly, wanna use q one as a little bit of a catch up, a little bit of a cushion because as a first release, there will be probably some anticipated bugs. There might be some very small enhancements we can kinda go ahead and be able to, you know, tackle. And wanna make sure we can do those things in a good time frame so that when we go to release it, we can do that around the q two time frame. So, that's really why we have it shifted by a little bit. It's really just to help a little bit of the padding so that after the first release of these two, main topics, Versus Code and Git, we can get those in and fine tune for the, 08/23 release. Now this might be, it should be a familiar timeline. The difference is that in the past, I've used it for 8.two. RSA 8.2 is not part of this anymore. That's since been retired. It's really concentrating on eight dot three. Eight three was released, roughly three years ago now. It was the early part of q one back in 2023. We're now May 2026. You know, we've already done patch update one, And, that was a little bit delayed primarily just because it was at the tail end of Micro Focus, switching and transitioning to, OpenText, and then we got acquired by Micro I'm sorry, by Rocket. And so for that, you know, there's some policy changes and things like that that we had to be able to adapt to, and that's why it was a little bit delayed. But at the same time, we also had a chance to make it, much better in terms of adding more enhancements. I think at that point, we had almost 40 customer defined enhancements, going into it. The latest release that just came out patch update two, eight three two, had just been, released about two months ago. Hence, why we have the what's new that's coming. And you can see that in for q two, I have the placeholder for eight three three. As we get closer to that, we'll have a physical date, or close to a timeline within about a two or three week period. But as of right now, it's it's really just slated for '2. And then we have it really the timeline going all the way till 2030. EOD, as you can see in my notes, and it stands for end of development. Ultimately, it means that when we're going to retire the release just like we did for 08/2002. And you can see that we have the active stream and we have the save, stable stream, going in session. Normally, what we've been able to do is predict that patch two of any particular release, would end up being the last or final patch update for the, quote, unquote, active lease stream, which you can see that four eight three three, that's really gonna be our final patch update for the active lease stream. And, again, it's really because of the amount of work we're putting into both Versus Code and forget, anticipating that we're gonna be, you know, breaking changes and so forth. Also, there's a good healthy backlog that we have that are around, you know, customizable components. We wanna make sure we get those things in. But once we move into patch update four and we're anticipating about three patch updates, I don't think we're gonna, you know, mirror, eight dot two. We had a patch update seven. I think we're gonna be patch update six. So four, five, and six will then become our stable release stream. That's where you're gonna have, easier upgrades. There won't be any custom customizable components in there. It'll just be executable components. Much easy to go ahead and do an upgrade, you know, from one release to the other. But there's still gonna be a little bit of that pain, you know, with patch update two and one more patch update three, and then we'll transition over to the, the stable release. Just a level set for Versus Code and Git. The RC, we do have both integrations today. We have, you know, Versus Code integration, which is a lightweight casual integration, and it was designed for that because Versus Code is a a an editor. It's not an IDE. However, over the last twelve, especially eighteen months, we've been getting a lot of feedback from customers to say they wanna be able to use Versus Code more as an IDE integration as opposed to a lightweight. And so we're really taking that, and we're going to accelerate and enhance that one so that you can become more much more viable to your your, your organizations. And for the Git integration, today, we have the GitConnecto, and it does, work very well. It does your push, pulls, your your commits, your merges, and your clones. However, for customers that have Git today, they've informed us they want Git to become the master repository as opposed to ChangeMin, which is how the Git connector works today. Secondly, the Git connector really is limited when it comes to Git workflows, and that's something else we're going to to tackle and and, and resolve. Thirdly, is that when the Git connected was designed, it really was the, the user we sort of anticipated was the Changeman user that's now going to start to use Git. So they already have familiarity with ChangeMan, and so that was sort of, like, the strong assumption we went with. However, we found very quickly that the typical user is a native Git user, someone who has no experience whatsoever with ChangeMan. And so it makes it harder for them to adapt to the Git connector. Even though it does Git things, you don't need to do a ChangeMan Git command. It does all native Git, but it does have this sort of, you know, expected understanding of how ChangeMan works. So all that we're basically going to remove as, as friction, and we're going to be building a, different type of integration that removes all of that and makes it easier for a native git user. Also have it so that the repository, the master repository is Git, and it's gonna do a lot more than just the simple push pull commit merging clone. It will support all the Git workflows. Now how do we get there? We're getting there because we're working right now directly with a number of our our ChangeBank customers that have, Versus Code and Git as their priority. So now becomes our priority. And we're working with them. We shaped a lot of the requirements. We we validated, with a couple of customers right now. We have our first larger exposure to this with customers, in our customer advisory council. This is, in the past, you might have heard of a customer advisory board, back on the Serena days. We haven't had one in a number of years, so we're having our first one next year. I'm sorry, next week. And, as part of that, we'll be able to validate, a lot of what we're planning to do for both Versus Code and for, the Git integration. This is where you come in. You know? So for the the broader customer experience, we wanna be able to now have customer facing sprint reviews. And so I'm planning two to three of them over the next six months. This is for any Changeman customer. You don't need to be, you know, someone who only wants to participate, with us directly. You know, we'll still have those customers specific to the beta program and whatnot. As we close to the beta program, this is where I want to look at the surveys and really pay attention to any sort of trends around adoption around Git as well as Versus Code. And for customers that are really looking into doing it now, today, or yesterday, those are the ones we wanna be able to partner with. And at that point, I wanna be able to go ahead and start working with you directly, pulling you into conversations with our engineering team, pulling people in like Bob and Preethy as well, for that. The beta program, has not been truly defined just yet, but we're looking at q three. For that, about 10 at most 15 customers. We really can't open up more than that. It becomes too unwieldy to go ahead and manage. We wanna be able to, you know, really shorten that, feedback loop back to the engineering team. And then we'll have the initial product release for both, Versus Code and Git, really right at the end of the year, as as I said. So for those who probably looked at the, the timeline we had back for the virtual user group, you might remember it staggered. You know, the Versus code was at the end of the year, and then Git was really the first part of next year. We've actually been able to pull that forward. So a lot of kudos goes to the engineering team to be able to do that. There was a lot of work on their side. There's still more work to do, but they at least been able to do the architecture and get that straightened out, get all the design pieces there. And then over the next, you know, four to six weeks, I'll start to schedule that first customer facing sprint review for customers. You know, even if you have no interest in Git or Versus Code right now, it might still be beneficial to see where we're headed, you know, for the future. And certainly for those who, you know, it is very important for you, then let us know so that we can start incorporating you into these things more regularly. And, you know, before the beta gets too big, I wanna be able to pull you into that and at least, you know, target those customers as we get ready to start, that formal program. At that point, Bob, I can, bring you back. And then, if you wanna take the next fifteen minutes or so and review, some of the highlights for August. Great. Thanks, Jimmy. Alright. And, well, welcome everyone. Let me, let's let's just go on to the next slide. So just wanted to go through some highlights with this slide, and then what I've done is gone to the, Read Me from eight three two and pulled out some specific ones that I wanted to, make sure that we covered. So, you know, when you when you look at, you know, what's available, in eight three two, it breaks it into, you know, multiple buckets that, we put here. So enhanced, you know, change package visibility and control, and there are several, things that were put into August around that that whole topic. So we we put in several improvements where we've streamlined the the, change package management. We've really strengthened the life cycle governance governance concept. Several of the enhancements include, you know, clear visibility into, unavailable package actions where, you know, maybe before it wasn't there, additional request or information across, things such as list, query, approve, workflows, And then we've expanded metadata passed back to exits to support automation that you may have, either put in or you're looking to put in, to to, you know, support auditing and and any integration processes. So that was one broad area. A second one is d b two. So so those who have done a lot with d b two, obviously, you recognize the importance. But in August, we delivered several targeted updates that make the d v two change management smoother and more reliable for you, including, for automated bind copy operations and enhancements to the inter object dependency handling, improved error reporting. All of these updates help simplify the the database related processing, for d v two. Then for those who have ERO, the enterprise release option, and we do have a number of customers with that, not everyone. So if you do have it though, we've strengthened the our ERO capabilities, improvements that ensure data integrity, enforce more consistency, during promotion behavior with ERO. We've corrected some usability issues that were brought up to us. This includes things like validating e r ERO related d b two tables before allowing the release workflows to proceed. So just doing some prechecks before we actually jump into things, and then you go to take an action and received an error. So we're we're doing some of that validation upfront now. We did refine the package promotion rules. We did some corrections to, release archive processing and did some things with panel scrolling behavior and component operation. The fourth overall area that, eight three two focused on was improving both XML and web service support. So we did a whole bunch of updates to improve the reliability and correctness of XML based operations and rest services. They included corrections to the, XML message, XML service message handling, and then improvements to Sernet configuration. And I'm gonna go into detail on some of this. That's used by both XML and TCPIP processing and then enhance some validation around the rest server administration. And then finally, Cernet performance and reliability. I'll also go into a little more detail on this. We've introduced some new Sernet options that improve performance and reduce storage related events during, you know, heavy processing when when there's a lot of activity. Some of our larger customers were noticing that, especially during times of heavy usage. You know, if if you don't have a an exceptionally large shop, you may not have noticed that, but you can still benefit from some of the things we've added into eight three two. So additional updates included tunable TCPIP, what's called keep alive behavior. I'll go into more detail in just a bit. Customizable resource naming, and improve hybrid mode XML data retrieval and and corrections to ensure component master data is extracted, properly. So let's hold on. I'm in. I need to go back over here to go to the specifics. So as I said before, what I did here is just went into the read me for eight three two and pulled out, you know, a dozen or so of the features that I just wanted to do some additional focus on. As Jimmy mentioned before, we normally try to to to do a, a demo of some of the features. And you'll notice that a number of these, there there really isn't a lot to demo. Some of it's behind the scenes work. So, we just didn't do it here, but we will do that in future. So one of the things I wanted to highlight, new release admin option to allow package audit listings to be checked in without affecting the area audit code. So, focus more on, ERO. But if you're familiar with that, you can now check-in those, audit listings. We also allow to check into a blocked area. So if you've set that up In this release, we've added extra messages, that are written to a CMN write output to confirm what has been written to the PMAS by way of, source components, included copy information. So take a look at that. Talking about some of the performance things we did with Cernet that I mentioned earlier, the SV area, alright. They're talking about above and below the line. So this is a Cernet keyword, and it helps prevent, below the line, eight seventy eight ad ends during those periods of heavy user activity by allocating the initial user subtask, above the line. This is now the default setting, and in previous versions, you'll note that, this was allocated below the line. So if you look at your release today, you'll see below the line. We've now changed that as a default to above the line. If for some reason you still wanted it to be below the line, you now have the, ability to change that. But, yeah, I would probably leave the default. Another Sernet thing was the TCP keep alive. So this keyword parameter allows installations to to tailor the, the socket as needed to suit whatever specific requirements. The default is thirty minutes. That's not changed. It's always been that. But, you now have the ability to change that if you wanted to. So, you know, just take a look if there was a problem there, on your your end. You could increase that time if you wanted. Just, you know, be aware increasing that, you know, may cause other issues. You know, I wouldn't just change it as the administrator. I would talk with your your systems folks security just to make sure. High level qualifier, of the resource name associated with Surnet connect keyword parameter can now be specified by customers in SIRL CSAC. Previously, this was hard coded. You can see there it was serena.connect. Obviously, now that we're part of, Rocket, we wanted to change that, but we now had made it, instead of this hard coding in rocket, we've made it so that, you can name it to whatever is needed. And we provide an exit call time out parameter. This one, I I really wanna spend a little more time on. So, you know, for a number of years now, we have been really encouraging everyone to take advantage of high level language exits or HLLX. If you're not familiar with that, just a real quick commercial for that. That allows you to take all of your customizations out of the ISPF dialogue panels and put them into HLLX. That's gonna give you two benefits. One is the next time you go to upgrade, now you don't have to worry about carrying forward those dialogue panel customizations. They're just in high level language exits, and they'll work with the with the new release. So that's first thing. But the second thing, is becoming even more of an issue, and that is what happens if you have users that aren't using the traditional ISPF interface. They're coming in through an IDE. They're coming in through Versus Code. They're coming in through Git, some other interface. If you have customizations in ISPF, those users would not be able to see those customizations. You know, any validation, whatever it is you're doing, they would not see them. By putting them into the HLLX, they will now participate and see those. So that's the that's the great thing. But, there's a couple of issues that that, you know, we wanted to address, and that is, this call time out parameter for the HLLX exits that's associated with the z m f subtask. So change band z m f. Right? The task, it's always been there. It automatically, for those who don't know, can spawn off the h l l x h l l x subtask automatically. But what happens if, you know, something happens and it's long running, I e, you get into some type of a loop? So you can see here this talks about looking at the HLLX getting started guide for details. I actually have that up on another screen. There's too much here for me to drop in the presentation, but I encourage you to look at the, HLLX getting started guide. If you just do a search on, say, the keyword of time out, there's a section called HLLX conversation time out, and it goes into a full explanation. So you have, essentially, you're just adding a parm, and then you have the flexibility to make that parm whatever you want. And there's a there's a lot of explanation there as far as the parm. There's also kinda tied with that, something called HLS call time out, which, again, is something that you have the ability to change. And I encourage you to look at both of those because they serve different purposes, but really they work together. So, when you go to 832, take a look at the, not only the read me that we're going through here, but look at the HLLX getting started guide so that you can add that parameter in. I'd highly recommend it. Okay. Let's go on to the next slide here. So some other things that we've done, we've increased the number of available notify URL addresses. Previously, that was one. Now you'll see that that we've increased that to four. And because of that, we've eliminated and and this was a holdover from many years ago, something called the ALF filter, a l f filter, DSM. It that is no longer needed. So we've eliminated that from the started task. So, you know, when you do the upgrade, obviously, you'll see it, but, just understand that that was intentional, for us removing that dataset name. So that makes the log filter so there is no need to shut down notify URL task of the z m f task to change the log events filter. And you can see there's a whole bunch of sub points there. I'm not going to go in and read all of those. But I think the key is is that, these now can work independently. Right? So there's four of them. You can see there. It's notify URL, then, or n t f y, then n t f zero URL, one URL, and two URL. Don't let that throw you. So I know some people may think they they should be 1234, but it's notify URL, and then zero one two. Okay. We've enabled multiple SERP print steps in jobs, so you can now work with that. And then we've, modified so that there's more consistency in the package list and query selection criteria panels. You can see there selection, criteria panels that were only available in one or the other are now available in both. So, again, consistency, that, you know, probably should have been there all along, but, it's great that it's there now. Just a couple more things here, and I'll finish up. Whoop. Meant to move forward and did not click the button. There we go. Package requester name as well as phone fields have been added to the package list. Query and approve selection criteria panels listed there. They're now also passed to assembler exits and to approve scratch rename and exit nine, in HLLX. Option u, has been added. So, you know, a lot of times, it it's it's interesting. We'll get asked inform or or we'll ask an account information or a user to say, well, you know, what release are you on or what is this or what are that. And a lot of times, they're not able to find that. Right? Because when you bring up change, man, that splash screen disappears pretty quickly. So option u now is about or ChangeMan about, and so there's gonna be, a number of, items there that are useful information, that that, you may need to use internally or you can share with support or whoever. So just, be aware of that. A new primary command. This this is kinda cool. It makes life a little bit easier called delete all as well as a new line command. DD is available in the package driven stage panels so that you can do mass deletion of components. And you'll notice there the note under it says the new mass delete process bypasses the confirm delete request panel. So if you take advantage of that, it just makes it a little bit easier if you were trying to get rid of a large number of things. You're not having to go through the confirm for every single one of them. It's gonna bypass that. Component staging versions, now saves the user ID date and time from where the source component was updated instead of when it was built. So, again, there was a a couple of accounts that had pointed that out. And then another usability is during component checkout. That message previously was a pretty static message, and now you'll see we've, modified that. So you can see in the bullet points there, it'll give you more precise information about checked out, a specific component name from where, if it's a single component, it'll say component. If you've checked out multiple, it'll say components, as well as the the source coming from the baseline or promotion library, etcetera. So, again, a number of usability things that, we were able to put in. And then the final things I wanted to make sure we covered, and and one of those I've highlighted in yellow, but let's try not to focus there first. Let's just start at the top. Cancel command p f 12 now works on the monitor panels that are listed, and and it, returns you to the prior panel. Package user variables, for those who are familiar with the package user variables, normally, we're we think about, you know, in just a simple package, but they can now be updated for complex and super packages. They're now displayed when creating the complex and super packages they were not before. Displaying package user variables in browse mode now displays blanks instead of the word no, if the variables are indeed blank. That used to confuse people because they would see no and think, wait a minute. I didn't put anything there. Now it'll actually display blanks and not the word no. And then you can see several other bits there. Second to the last, the maximum packages with component setting global applications parameter now also applies to scratch and rename. Notice this the, sub bullet there. If this setting is one, a component can only be in one package at a time, preventing conflicts during check-in, check out, scratch, and rename. And then the final one. So this is something that was was kinda forced on us by the Apache community, the Apache Tomcat Tomcat software previously distributed with ChangeVAN. It's no longer supported by the open source community, and no newer versions are available. So as a result, Tomcat is not included in new change band releases. So before patch two, you'll know that we normally included that. And so, you know, a lot of folks took advantage of that. If you did, now that's not included. So you'll need to install a supported version of Tomcat or, you know, WebSphere or whatever, some alternative, you know, web server, for the Changeman web applications. You can certainly look in the, the web services getting started guide, you know, as far as installing Tomcat or whatever is needed. So, again, make sure you're aware of that, especially if you're using, you know, Tomcat that we provided because when you go to eight three two, you'll need to now add that to your task list as the administrator. Alright. So with that, I believe, my slides are done. Let me just go ahead. Yes. They are. So Jimmy's coming back. There you are. Back to you. Hey, Bob. Yeah. Just a couple of questions that came up, probably just the tail end of my section and, before you all started. I haven't seen any, for your piece come up yet, but you might see that as I I go through a couple of these questions. They're a little bit related. I wish I could share my screen. I cannot. Nope. But, what came up was, end of support dates for 08/31, August, August, and then someone had asked about the base version for 8 dot three. So just just to do some some clarity, you know, this is really a policy we've had going all the way back to the Serena days. We've just been able to keep that forward whether we're Micro Focus, OpenText, or now Rocket. There's really two different things I just wanna just point out. We have what is traditionally support, and then we have development. And they're really two different things entirely. So for a customer, on any version of Change Man, as long as you are paying maintenance, we will always support you. The support is going to be if it's an old on an older version, we can't, you know, quote unquote, do a bug fix. We can't do a hot fix against it. We'll always do, best effort support or around that, and that's what you're paying for. You know, a lot of times, there's already a hard fix for something that you might just be encountering now on an older release, and the team will work to, you know, rectify that as best they can. When it comes to an older version of the of the, of software, if it's change man, it could be complex, whatever it might be, we do draw a line when it comes to development efforts. You know, we we just really can't fix every version that's out there. You know, we have to draw a line somewhere. So when it comes to, supporting it in the sense of, supplying engineering fixes or even low, small enhancements, we only do that to the current release. So right now, there's two releases that we actually still have available right now. There's eight three one, which has actually been out there available for a little bit more than a year, about eighteen eighteen months give or take. And then we have the brand new release version of eight three two. And we always have what's called like a a six month grace period. We never wanna cut customers off at the knees to say, okay. You must go ahead and upgrade immediately to the latest release. You can stay on an old release for as long as you want, and we'll support you. It just means that if it requires any level of development, you do need to be on the current release for those things. And so for 08/31, the, quote, unquote, end of development is not gonna be until August. I think it's August 12 to August 13. Essentially, it's six months after, the current release date was released, and that was released in February 12 or thirteenth. It might be the thirteenth, which is was on Friday. So that would mean that a three one is available for any kind of development effort. Could be a hotfix, could be a small enhancement, whatever it might be. Those things get prioritized just like everything else. And, you know, once it's been out available for six months, which is the current release, that's when the prior release, in this case, a three one, would be end of development. The going forward, it's the same thing for eight three two. When does that become end of development? Well, that would be six months after eight three three becomes released, and then so on and so forth all the way through the last patch update. And then hopefully that answers the first question in terms of, you know, when does something become end of development. I know the question was end of support, but we always support you, So that never goes away. It's just only about end of development. The second question was what about the base version of eight dot three? So when I answered that, I was talking about the first initial release, eight three dot zero. No. We don't call it dot zero. And that's the same thing. That had an end of development date, I think, of, May 2025. So, ultimately, this time last year because that was six months, after eight three one was released. But eight three in terms of the release train, that won't end until sometime in twenty third. It's it's really out there for a while. That's why we anticipate having multiple patch updates, for the remaining, what, four years that we have. We're gonna have at least one more patch update that will be part of the active, stream, which is gonna be both customizable and executable components. And then we're gonna have we're anticipating at least three, patch updates that would part of the stable release. That'll be eight three four, a three patch update five, and then finally, a three patch update six. And that brings us right around 2030. Now it might go into 2031, and that's all the better for our customers because that just means it gives you that much more of a runway, that much time with a mature release. And, you know, right around the time or in between patch update five and patch update six, you'll probably hear from me again with the the same sort of timeline. And then we'll be talking about the next major minor. And whether that's gonna be eight dot four or eight dot five, it's too I'm sorry. Eight dot four or nine dot o. It's too early to to kinda predict that right now. But then then we'll go, you know, from, having a stable release for 08/03, whatever is remaining there for the patch updates. And then the next major minor will then move into the active release three where the next, you know, two patches or so will be, you know, having both customizable and, executable components. So hopefully that that answers, you know, those two questions that came in. Bob, I think there might be some things for you if I'm looking at the, some of the questions that came in. Sorry. Looking at the questions now. So your, the the one from Stefano, is it planned to introduce static source version keys rather than the current minus one, minus two, identifiers, which are dynamic and change to some a new version is added to the baseline. I'm not aware of that, Stefano. I would encourage you and and I don't, you know, not not positive you've not already done this, but if you've not already submitted an enhancement to to, you know, point that out and to suggest that we make that change, please go ahead and submit an enhancement so that we can get your specific, you know, requirements. We can let, you know, others internally to to, you know, kinda, bat that around and and talk about it and then, also have other customers vote on if that would be beneficial to them. So, Stefano, please go ahead and submit an enhancement for that. Yep. And and probably same thing for the next one you have, Stefano, which is, any plans to support searching for string across all baseline versions of a component by XML, or rest interface. I'm not familiar with that one either. So, if you haven't already, please submit enhancement for that one. You can do that right through the ideas portal. If you have, let me know, and I'll I'll look for that, to see where that might be. I I can say that's not part of eight three three, just because I I I know what's in there, for the payload. But, we can slowly see if we can, you know, look at something like that in the future. Yep. The other question oops. Sorry. Go ahead. yeah. I was just gonna say that there is currently some, and I don't know if this does exactly what you want, Stefano, but there is some search capability for strings, through ISPF, but I'm not sure if that does exactly what you're looking for. So, again, if you could submit that enhancement request, we can take a look at it. Or if you wanna, before doing that, you wanna shoot me an email, you know, we can go back and forth just to verify if what we currently have works for you. And if not, then you can open the enhancement. Sorry, Jimmy. No. No. It's too great. Then there's another question here regarding the beta version for Versus Code and or Git. Who can you reach out to? Myself. So if and if you don't know how to get in touch with me, at least start with your account executive. You know, you might already be working with with Bob, you know, on other things, or you might even be working with, our other presales engineer, in EMEA. Reach out to them, and they can get in touch with me. I definitely wanna start that process probably the next two, three weeks. I wanna be able to line up the specific customers because, once I have the customer facing sprint review, right after that, we'll be starting to look at, more specific things with those customers around the beta. You know, we'll probably still be too early for the full beta program. I wanna make sure that, folks like myself and Bob and and others as well as the engineering team know which customers are gonna be, participating in that, because that'll be very vital. Have any other questions that came in? Sorry. Go ahead. There was something else you wanted to add. Now I was just gonna remind everyone, while we're finishing up the q and a, if you've not done the survey, please go ahead and do that. That is vitally important to us. So please take. some time, to do that while we're just finishing up here with any final questions. Yeah. It it shouldn't take more than maybe thirty seconds, but, you know, we're gonna we're gonna keep the the portal open, I guess, for about two minutes after, this closes just to make sure you have time, for that. But, it is very important for us to kinda figure out what the trends are and which customers do we wanna be able to target for, the customer facing sprint reviews as well as more specifically the, the beta program. Okay. I think that might be it, Bob. I don't see any other questions coming in. I wanna thank everyone for their time. And I didn't say it upfront to apologize, but just like anything else, you know, the recording will be available usually within about twenty four hours after this. It'll then get posted. For those who have registered, you know, you'll definitely get a a link. And certainly for those who attended, you know, thank you very much for the time. I appreciate it. Thank you very much. Thanks, all. Bye bye. Bye.