I get that the Wordpress crew likes you to upgrade ASAP.

BUT...

I just spent the last 4 months skinning, tweaking, writing plugins for and modifying Wordpress for a corporate blog. When I started, 2.8 hadn't come out. When I deploy, it has to go through two other teams before it hits the live webserver. It's tested, prodded, punched, poked by at least a dozen people. I simply can't "upgrade" on a whim. It has to go into our version control. It has to go thorugh all these people. Wordpress 2.8 came out early June. But from July 9 to Aug 12, FOUR minor point releases came out. FOUR. I can't push those through at all in that timespan.

I recognize that that's a pain in the butt. I recognize that it's stupid to have to do thigns this way. I don't want to. However, it is a corporate reality for a lot of us.

Why is there no maintenance at all for previous releases? I can't expect it, I get that. But to drop support for a version of the software so quickly... seems crazy to me.

There are some changes from 2.7 to 2.8. None so huge that it won't require but a little work. It looks like there are bigger changes that will affect me from 2.8 to 2.9. I can't just roll out as soon as they come out.

I would beg the Wordpress team and Matt to consider backporting some of the security fixes. I would beg you to issue a patches, not a full upgrade. Tell us when the DB is changing and when it is not. Make it EASIER for us.

The release schedule that has been set since the 2.0 release means a new major point version every 3 to 4 months and having old releases completely unsupported, I can't help but think I'll fight harder to not use Wordpress in future at work.