guff

I’m glad that this has been “the quietest major point version release in the history of software”, and it should remain that way for at least a few more days. The whole wordpress.org site was incredibly unstable for the past few days, and that has finally been fixed, but the forums are being flooded with tons of nasty error/bug reports from this release. This is not a finished product. If you want my advice, I suggest that you wait for v2.0.1 or until they mysteriously roll all of the changes from the past few days into the download archive without bumping the version number. If they do that again, like they have for the past few updates, then it should happen shortly before the public announcement on the official WordPress blog. Honestly, they should have waited until sometime in January to release this. If they had, then they may have had a chance to fix a few more bugs in WordPress v2.0 and bring the new wordpress.org online without breaking everything.

“This was a major launch. It has been thoroughly cocked up.” ~ Podz

“This is not a finished product.”

Here you come to the crux of the matter. Or issue. Or whatever. It’s the reason why there’s been no fanfare. You don’t start marching around and waving banners in front of a parade which hasn’t finished construction on the floats. It would be good to see someone come forward and admit they (well, we, sort of) jumped the gun. Otherwise the WTFs will only start to grow exponentially.

Thanks for helping me with my comment question. You were able to help me! I appreciate it.

I just upgraded my WP yesterday to the 2.0. I didn’t know anyone using it but thought I’d try it anyway. Not sure why. I haven’t had any major issues (the only problem I’ve had, at all, is the link button isn’t working/doesn’t link my text) but I just do it manually and not complain. I hope I don’t have any major issues… :)

The only reason it wasn’t announced is because of unexpected and unpredictable server issues. The 404s sucked, but on the bright side if we had stayed where we were before the site just would have been inaccessible.

When do 404’s not suck?

Nevermind. Don’t answer that. In case there actually is a reason for them not sucking, I don’t want to know. I mean really, 404’s *not* sucking? WTF?!

Ah, sorry about that implication. Your comments here were also interesting to my post, though.

No offense taken, Owen. WordPress 2.0 may be a Not Ready for Prime Time player in a few specific areas (none of which begin with “new feature X sucks”), but with proper precautions going forward with the upgrade *can* be a good thing. Education and preparation are our friends.

But you did get me to do my Hulk impression here, which I haven’t previously. And for that, thanks.

i do agree that wordpress 2.0 was kind of “taken for granted” in a way, then again, it almost doesn’t even seem stable or “ready” to me - i don’t know, it’s kind of weird.

I would just like to add to my previous comment that I have finally upgraded to WordPress v2.0. I did encounter a small problem with the generation of my pages’ permalinks, but that was solved by incorporating the latest changesets from the WordPress Trac.

This is not a finished product.

I wish I had read this before upgrading. It seems the new way WP2.0 sends trackbacks doesn’t work on certain servers (mine and many others are reporting 100% failures, trackbacks are never sent). Going back to 1.5 alleviated my headaches and I am going to wait for 2.1 to try again.