Releases do not happen on any set schedule. When a change is voted on, it is queued to be added within a reasonable time frame, not necessarily immediately.
So then, I want to clarify ratification: it happens on the first voting phase that is at least 30 days after the release date of the version with that change? (So almost always more than 30 days, if a release happens in the middle of the month, which sounds reasonable, it would be about a month and a half)
I assume it doesn't just happen 30 days after, seems like a lot of work to have individual dates for ratification.
And what about a change that was released later (let's say the modder didn't have time to implement it while everyone else did so a version was released)? It would be ratified 30 days after it's sub-release, right? Also, the delayed release should count things like a feature being implemented but broken by a bug, so that the release is when it's released as "working", ie. the latest release that changes that feature as only bugfixes should be posted through non-VP Congress.
This makes me think of an issue, that if the VP version isn't released at the start of the month then what are people proposing changes for. It could very easily take 15 days to make a working VP version in which case people are suggesting changes for a version they've never played. Of course they could base things off of what they *think* will happen, or what were issues last time, but it's a little limited.