We do have other people in the office programmer leads Developers who can push out patches.

That's not the problem.

The problem is that like we talked about last week on the dev stream the initial size of patch 2 for exp 1.2 exp on PC Scope crept so we had one vision of what this patch was gonna be and

might want to log out of teams before we move on to the rest of the stream.

Thank God for that, actually.

Oh shit.

I'm gonna have to go and personally thank Max later.

Max, you just saved our asses again, thank you.

Anyway... Yeah, we had an original vision for what patch 2 was gonna be on the XP and that patch scope crept.

And what happened when it scope crept was we had one branch

for patch one, first and foremost.

Developed after feedback and after internal discourse.

We tested on the same branch and we shipped from that branch.

Patch two, took over that branch, same thing.

Took feedback, we had our own internal discourse.

developed and mostly finished up on that branch, but then when the patch scope crept, it scope crept by an adjacent, a second branch being opened next to this first one, and on this branch is where we have, I think, Uzu, not Uzu, Guru counted 14 fixes, pretty nice substantial fixes, both back and end visual bug fixes.

that we really want in as well.

And for reasons that I'm not gonna dive too deep into, we only want to patch one more time.

And so we've committed to shipping both branches at the same time.

Now, the first branch with the OG vision, that's actually fully tested and technically with ship.

But again, we do want both branches to be shipped at the same time.

And the second branch was what was going to go through a final, pretty thorough QA session.

But that's when Uzu turned... Greed.

Greed.

And is now gone.

And we do have QA staff on site, but they have so much to do.

And Uzu is the one delegating priorities and proper tasks to QA.

And he was not around to do that.

So what QA reasonably can do, according to just the road schedules, is work on the shit they already know they have been handled or handed.

And so they will hop onto that adjacent branch when Uzu is back and when he has delegated that stuff to them.

And when that has been tested, that's when you will get patch 2.

I would count on that being early to mid-May.

So yeah.