How does the late release of 3.10 impact the upcoming 3.11 and 3.12?
TL;DRTeams start their planned sprints when the quarter ends, and the impact of a late release depends case by case on which teams are pulled onto must-fix bugs versus feature work.
So basically when the quarter ends, we already have plans for every team and what they need to do, all their upcoming sprints and so on and so forth. So as soon as that quarter ends, those teams actually start working on it. Now, if a Live Must Fix bug comes in, or something that I feel really needs to get fixed or John feels really needs to get fixed or any one of the other directors, then we pull somebody off to fix it, and then they go back to their sprint work. So it will really depend on the team that is working on it. But for example, let's say we shipped 3.10 right at the beginning of July. And let's say targeting wasn't working the way that we wanted it to work. That team would still be working on targeting. We wouldn't just be putting it down saying, okay, it's good enough. We would continue to work on it and basically adjust other plans. In essence, it really depends on what team is being affected, but for the most part, a lot of our bugs are just somebody going in, recognizing, oh, that needs to be fixed, and they fix it, and then they go back to their feature work.
Different levels, basically. Some teams are going to be affected more than others.
Yeah, and even then, for example, if it's a moderate bug or a trivial bug or something like that, we take it on the chin, we're like, okay, we're not going to fix it this patch. We'll move it to the next one, and basically we'll allow them to continue on their feature work, because we feel like that's more important versus a moderate bug or something like that.
But each on its own case-by-case basis. It's not saying that features are more important than bugs.
Yes. And the other thing is that we have a label that we call gameplay experience. So anything that has a gameplay experience bug that is a trivial or a moderate or anything like that, I view those as extreme. So basically QA flags those to me and I go through and I basically am kind of the judge and jury on those. I'll sit down and I'll review it and I'll think about it and then basically either assign the label or not assign the label. And then what we've asked the teams is to try to work through as many of those bugs as they possibly can. And even when they're triaging bugs or working on bugs, they're still looking at those and viewing those as, yes, I need to fix those before we do another release.