Is WordPress 4.2.1 the stable version?

It has bug fixes, so it’s going to be a very big recommendation to upgrade so that you have any security issues pathced before hackers get into your site.

I fond that most “updated users” have encountered the issues of white blank death error and plugin working error. Therefore, I personally want to wait for a few days until all the bugs are guaranteed to be fixed up.

I haven’t seen that, and that’s after updating ~40 webistes over the last two days, so I wouldn’t say that everyone has problems…

As far as waiting a few days, that’s not going to help. The code will remain the same until the next update, and if you don’t update until then your site will have an open and very public vunerability that could be easily exploited. If it was me I’d take the chance and update and then deal with any issues that came up rather then just hope that hackers don’t attack my site before I get around to updating. But, that’s just me… ??

Well 4.2 and 4.2.1 are obviously different and 4.2.1 was released just a few days after the release of 4.2. I havent updated to 4.2 and i am using the last stable version (from anecdotal perspective that is).

From what i have read it is 4.2 thats has the javascript comment exploit so assuming you havent updated to 4.2, i think its worth waiting for a stable version of 4.2 . But then again, im not a senior programmer so my coding knowledge is limited.

UPDATE: found it. Not sure if linking is okay here but the exploit is in versions 3.9.3, 4.1.1, 4.1.2, and 4.2.
I have version 4.1.3 which seems to be a stable version.

i think its worth waiting for a stable version of 4.2

Sorry, but that’s not going to happen. The “stable” (as you call it) version of 4.2 is 4.2.1. Anything after that will be 4.2.2, 4.2.3, etc.

I couldn’t find 4.1.3 in the repository list so I’m guessing that you’re running 4.1.2? If that’s the case I would suggest updating. As noted here, version 4.2 fixes 231 bugs from previous releases… and as 4.2.1 is the current stable version, you really should be using that.

Well it’s on my dashboard saying 4.1.3 and there’s this. But looking at the changelog it didn’t say anything about changes in core coding so the exploit in 4.1.2 would still be in 4.1.3. So 4.1.3 would in fact not be the stable version…

So I guess I really should update then… time for me to take the dive D:

Actually, the stable version of 4.2 is 4.2. Releases go through at least a month of publicly accessible beta and release candidate testing before the final release. Here’s where 4.2’s public beta testing started: https://www.ads-software.com/news/2015/03/wordpress-4-2-beta-1/ and you can see the other releases in sequence under https://www.ads-software.com/news/category/releases/

4.2.1 is just a critical security fix and one very minor code cleanup. Fixes for the known issues that can be fixed are in progress, but please note that some of the known issues are due to plugins, themes, and server configurations, not WordPress.

4.1.3 was a critical bug fix for the critical security fix in 4.1.2, but it’s not as well known because 4.1.4 was released as a critical security fix shortly after.

Remember, we’re referring to software here. There will never be a bug-free version of anything. Just look at Windows, Mac OS X, iOS, Android, your favorite browser, your favorite office software suite, etc.

A release is considered stable when it has gone through the (at least a month long) beta and release candidate cycle and all reported bugs are addressed. It’s then released as final, but now it’s being used by millions more and their variety of configurations, so of course more bugs will be found.

If you’re interested in being a part of this process, or at least following along, development on 4.3 is starting tomorrow (April 29) with an intended release goal of August 18: https://make.www.ads-software.com/core/2015/04/28/wordpress-4-3-kickoff/