So as I've said here and there I have a background in software development. While currently that's rather limited, my formative "IT/IS" years were in professional software development, programming, design, etc.
In seeing the delays in 1.33 - my main point is one of procedure. This particular item is - 1.33 encompasses a *LOT* of fairly major changes.
As such, this should be considered 1.40; not 1.33. 1.33 should be for minor bugfixes, small changes, micro updates. Whatever. Slight additions. This I think represents more than just a simple numbering complaint. But rather an issue with the way Lee (I hope he sees this) is organizing his work and conversely how it affects the expectations of the community. For instance, one of the big selling points of GG is the lifetime updates. While I think this was effectively a massive marketing mistake, it's in there and it's part of GG's lifecycle. So realistically if you're organizing your time as a developer you should be breaking down the product into multiple phases:
1) Major versions - Huge changes, core updates, complete rewrites, etc. Game guru 1, Game Guru 2, etc.
2) Primary releases - big projects being done every 3-6 months for major releases. Usually designated as a X.Y (i.e 1.4)
3) Point releases - bugfixes, minor changes and additions, cleanups and optimizations - regularly done. Usually designated as X.YY (i.e. 1.41)
4) Hotfixes - Obviously there's the occasional major issue that needs to be dealt with. This gets usually an alphanumeric addition to the patch code (i.e. 1.41b).
Progress should be pipelined with some patches being bundled into Major/Primary versions, but 'safe' fixes being released via regular point releases and hotfixes. This isn't even something I consider needing done by major companies, but rather even very small developers.
The reason this is important is because software can quickly balloon out of hand. There's a lot to manage, hundreds, thousands, or tens of thousands of functions and features which if there's no organized method of deployment, can cause considerable confusion on when it's released. People start saying things like "why is X added when Y isn't even done yet?!" (sound familiar?
Anyways.. I'm not trying to beat anyone over the head here. I honestly think that all things considered, Lee does well enough as a one man army. I'm just hoping he sees this and maybe takes my recommendation at better processing and organization of his project(s) to better facilitate his and his team's time.