@alex I'm replying to the above comment. This may be long. ;)

WordPress has a real problem in not having a “stable supported version” system in place.

1. WordPress does not have that problem and every release is a "stable supported version". I'll circle back to that.

Give people the old “my way or the highway” just isn’t possible in this sort of a product

2. No one says that, no one does that. But someone disliking how the development model works is not the same as saying to you "get lost". It really isn't.

Considering the investment and the time spent on existing projects, there is no simple way to “just move away”.

3. No ones asking anyone to "just move away" and moving away is not a solution to your problem.

I complain because I care. I want WP to be better, I want it to be lighter, I want it to be less of a resource hog, and I want it to be less of a security nightmare looking for a place to happen.

Don’t you?

4. Oooh, I like that one. It makes your problem into "I care. You all disagree with this. Ergo you must not care for WordPress users".

See why I like that one? ;) It's not on point but does manage to get away the real problem here. It's a distraction and I am 100% positive that people will not only like that comment but use it as an often repeated battle cry.

Now to address those items.

Item 1: There has never been a test branch of WordPress and all WordPress releases are stable.

That does not mean users have not had problems with some releases. There is a lot of add-on code in the form of themes and plugins that either are just doing it wrong intentionally or without realizing it. Usually it's the latter and theme/plugin authors learn from their mistakes. Updates get released quickly for those themes and add-ons, you see that with every release of WordPress.

Add-on code gets better all the time. No one (generally) repeats the same mistakes in their code. But please don't mistake problems with add-ons for a WordPress problem. It's not.

Item 2: The replies aren't "my way or the highway" it's always been "Hey, work with the community, use the actual existing channels and make your case. If the case is persuasive then changes will happen."

These comments here about your problems? Not persuasive, doesn't make a case and last time I checked WP Tavern isn't the place to influence those decisions. Also the vitriol doesn't help especially when the complaint can be summarized as "Core Team hates users. Why won't the compromise?" A capitulation to reversing design decisions that were made in line with the design philosophy isn't a compromise.

See Hugh's guide for how to get involved. That's a good place to start.

Item 3: When a WordPress release happens the best place to check the temperature is the WordPress support forums. Almost a year ago I wrote this in the make/support blog.

Please report any 4.1 related issues there and update the OMGWTFBBQ post as needed. If needed; it looks like it’s been a smooth release* in the support forums.

There have been releases that have generated A LOT of support topics in the WordPress forums. The stated goal of WordPress releases is to become transparent and issue free. That's actually happening; WordPress version upgrades are approaching the same success rate as Chrome browser upgrades.

That does not mean some users will not have problems. With millions of installations how could 100% success rate ever happen? But see Item 1 above and when you do have a problem, the support team wants to know and help you out.

Item 4: A litany of complaints does not work anywhere with any community.

There is a certain therapeutic effect when anyone complains. I complain all the time. Work, WordPress community, my commute etc. Who doesn't complain?

But I don't think my complaints work or accomplish anything. What works is getting involved and again, Hugh's post explains that very well.

If you are a WordPress user then odds are that the version upgrades will not effect you in any negative way. Just volunteer in the support forums, it really is an excellent way to see that.

If you are concerned about upgrades and that's good, then you (the user) really need to do the following.

a. Have a back up strategy. Store full DB and file backups off of your web server. Test them, make sure your backups work. I backup my whole network every night automatically and occasionally confirm that they're good. I use a plugin, there's a lot of them out there for free.

b. Build a copy of your live site either on localhost (sub-optimal) or on a second vhost (much better). Some add-ons don't work unless the service can get to your site and localhost won't work in that case.

c. Upgrade the backup copy. See how it goes. If it goes well the do it for real on the actual live site. If the live site goes belly up then you'll be glad you have a backup strategy.

*Re-reads*

Wow, that's a lot for a comment. I think "WP Tavern Comment Effect" should be a MEME.

Look, no one will take responsibility for your site, that's all on you. And there is no way everyone will be happy with what any group does. You and others do not like how the development process works and that's fine.

But please stop trying to identify your problem managing your site as a WordPress problem. It's not and my saying that isn't telling you to "take the highway". It's me suggesting that you manage your site and upgrades. That's not an unreasonable suggestion.