Is there any impact to Squadron 42?

John works on everything as well, but it really should help at the end of the day. This whole situation means that there's less downtime for people who are doing the Squadron work and have to support stuff in the PU. We have the longer development cycles, because all the Squadron features are in the PU. It's a shared codebase. So this whole thing should really help everybody in what they're doing.

The people that are working on missions for Squadron are having to work with the same stuff that goes out every quarter. Obviously they get it as it comes in, but if people are struggling to do a certain feature in the PU, spending longer to fix it means that the Squadron team gets that fix in a better state sooner, so it helps them.

In terms of our long-term roadmap, yes, I think you will see some changes to that. We're going to basically break down exactly where we're going with all the features and so forth to get them to where they need to be. And we'll be sitting here in a year's time and we'll talk about some other improvements we want to do and so forth. You can't stand still. You have to learn from your experiences and look at what worked. If you just blindly do the same thing over and over again, then nothing's going to improve. In CitizenCon last year, our plan is, when we have persistence, when we have some of these core features in, like the orgs working properly, which is part of this drive as well, when we have server meshing going, at that point we feel like we have a game. And that's what we want to get to. So while all this is going in, we're cleaning everything up, we're polishing, we're making all these features work great, we're adding all the sub-features in there and so forth. And at that point, we have a game that people can just play and really love. And then after that, every quarter, we give them more. We give them more. We give them more. We're then going to basically just keep on building on this for years to come.