There are reports of a few people who are running the latest trunk of WordPress on a live blog and that is a really bad idea. The merge of Crazyhorse is still being stabilized and there are quite a few areas that I’ve tested, on a dev site, that are currently broken.
I believe that the level of stability of the Crazyhorse merge is increasing and I expect I’ll be able to SVN Up to the latest revision. I’ve been keeping a watch on the trouble areas, but haven’t been reporting issues until it is stable.
I think one of the issues is that the new “Inbox” includes test data, that I really don’t want to have on my blog. Yeah, I can delete it, but I don’t know what it is for currently, and I don’t want test data on my live blog. Hopefully, for those who have updated, it will be removed, but I suspect that including that in the upgrade process might not make much sense.
That said, from what I’ve seen, it is looking better. I’m impressed with the features and increased usability of the new version. When everything works and it should before WordPress 2.7 is released, I think many people will be happy. If not a little bit upset with yet another major interface change, since WordPress 2.5. People will eventually find that the new interface is a lot easier and better.
You can already change the Administration Panels, if you don’t like the changes.
Who am I to suggest this? Well, you can do what you want. Just be sure you don’t get mad when it hits the fan and I strongly suggest you test WordPress locally. When I say, “Test” I don’t mean you just write a single post and see if that works. I mean you go through every page, hit every button, input every field (that you want to know working), everything! to see that it works. If it does, then let me know.
Possibly Related Posts:
- WordPress Plugin and Theme Scope
- What I’ve Learned From WordPress
- Why Do I Feel Like an Asshole When Criticizing WordPress?
- PHP5 Straw Man Argument
- WordPress 2.7 Changes Class for Plugins
Surely that goes without saying. You shouldn’t use any trunk versions on a live blog!
Dougal, well, I do use trunk. However, same with the WordPress 2.5 changes, I waited until I knew that the changes were stable. I’m usually about two weeks to a month behind until I’m sure my blog isn’t going to explode.
It is more dangerous than say, switching tags, but I do like seeing the new features. With the WordPress 2.7 changes, I could see that they didn’t do that much QA. After browsing through and finding half the actions that I do broken or unimplemented, I don’t think I’ll be “Svn up” until probably the end of September.
Of course, I could also help with the QA and helpfully fix some of the issues I’m having. I’m doing other QA at the moment and user testing should be automated in several areas, so I’m going to work on that instead.
WordPress 2.7 to stabilize some