From one vantage point, given all that has changed, it does seem odd to imagine that this major update to the software was only worth three tenths of a bump in version number. I can understand that. But is this release really Movable Type 4.0? No way...

Now I'm not going to tell you that MT 4.0 is already spec'ed out. It's not. However, we think we know generally what it looks like and how it's different from the blogging software and even general model of blogging you're used to today. MT 3.2 is a big evolutionary jump. We'll save a major version change for when it's revolutionary.

So why not 3.5? Well, honestly, we discussed the possibility early on but tossed it aside. This is a significant update in terms of usability, community management and installation-wide management, there's no doubt. But to get to 4.0, we have business to take care of and that includes several releases with much bigger features than what we've included in 3.2.

Jumping from 3.17 to 3.5 would mean we'd have to do an even larger jump in the next version. What's more, to shorten our runway like that would mean that we have to do more in fewer releases, which is counter to our desire to have a more rapid release cycle.

Finally, none of us are fans of the bad marketing practice of version number inflation. We'd rather you be delighted that such a small increment in version number packs such large features.

Anyway, we do appreciate the base sentiment in Dan's (and other's) post: 3.2 is an awesome update with great new features.

We agree!