 All right, this is going to be a very short talk because if requirements is working, that means you don't notice us. So let's get started. So we are doing fairly well. This cycle, we haven't really done too much. Most of our work was doing lower constraints and doing unbinding the requirements update process to allow per project requirements last cycle. And we just kind of kept on going. It made our job easier in the long run, really. So, and yeah, I don't know if you guys recognize that picture, but about a year ago or so, a dam in California did not have a good time. The biggest cause of all these type of failures is PyPy. People unpublishing things there, and that just makes me go yell at upstreams about stuff and various caps on things, but the caps we can handle more or less pretty well. So what we've actually been doing is not too much. Mainly documentation, which has been more over the last few weeks, we're going to try to get projects to stop using projects as requirements. And that means things like neutron, don't import neutron dot foo. That tends to not work so well, mainly because it's not a stable ABI that you can program against, and since it's a cycle with milestones, it means that you're not able to get releases throughout the cycle as well, because we don't allow beta or alpha releases or pre-releases in general, and the constraints. Beyond that, Python 3 stuff, there's been a couple small changes in there for us, but it's all been fairly simple. Publishing upper constraints is the last big thing that we want to do in the Stein cycle, where we will, for instance, with master, publish a Stein dot text for upper constraints and a master dot text, have all the projects target Stein dot text, and when they branch, they're automatically good, and they just need to change their master to target train dot text instead. So it makes the freeze process basically non-existent for us, but I'm going to try to work on that over the next month or so, just, it's holiday season. And that's it. I told you it'd be short. Any questions? It's short and sweet. I expect heckling. That's why I invited you for it. Can I do what? Sure. I could probably do this two or three more times than the time I have allowed, but Google, and then I limit by license I can use and resolution. This is actually based off of the other presentation I did. I just took the same slides and changed the text a little bit and shortened it a lot. They're pretty. I had to search for that one in particular. Master dot text. So projects, master dot text is just going to, I guess we don't technically need to publish it, but we're going to anyway, because it's, we're trying to publish per branch. And master is actually kind of two branches, but one of them's not branched yet. It's going to be both master and Stein in this case. Yeah. If we are supposed to be pointing to the cycle name anyway, why do you have that master there at all? Well, there are some projects that will want to point, post to master at all times. I think cycle with intermediaries probably might be one of those. Yeah. So it's going to get some use just not nearly as much as branch dot text or release dot text. Yeah. It, and it's not like it's going to hurt anything either. Like we're just going to constantly push to tarvalls.openstack.org and slash releases slash whatever. That's it. Yeah. I guess we'll be done.