How are the objectives for a release decided? How do we decide what goes into 3.1, 3.2, 3.3 and 3.4? Is it mainly based on time, or is it that we need this feature before that feature?

Yes. I mean, there's a lot of aspects to that, right? So the project leadership group for the Persistent Universe, as well as Chris, kind of go: with 3.0, we've laid so much awesome foundation for so many great things. And so now, what do we build on in that? And where are we at with each of those things, right? So if mining was in the R&D phase, but we've already figured out how to do it, now it's just about executing on it, great. Here's the tasks it'll take, now that we know more about it, and when we can get it done. Does that work for the project? Is that a good time to roll it out? So yeah, it's based on complexity. It's based on when that quarterly release lands, based on what we've established it would take to make it. Also based on what would be good coming in together. That's why you see some of those features planned to come in together. Object container streaming, as everyone knows, is a big feature that we're working on on the technical side, which will allow us to add more content and allow for better streaming in and out as you move through these large areas of assets. So yeah, there's a myriad of dependencies. It's not just a grab bag of like, I kind of want mining right around September, because that's when it gets colder out in certain areas of the world, and so I feel like I'd want to sit down and do a lot of mining. Does that feel good to you? Do you feel good with that, Crow? Yeah, let's do that. Maybe that's a factor, but that's a tiny factor. That's a real small one. But yeah, there's all sorts of aspects.