As discussed in the developer mailing list, the next release of WordPress will be in March instead of January because of the holidays and the amount of changes that will take place in the codebase as well as the admin section. The decision was made to consider 2.4 a skipped December release and move straight on to 2.5. The reasons for the change in the schedule include some good things cooking in the oven and the developers do not want this to become a rushed release.
So to sum things up. There will be no 2.4. Instead, we will see 2.5 which is scheduled for release in March. Various official docs and roadmaps will be updated in due course.
All good things come to those who wait.
Awts. I’m expecting that we will have the WordPress 2.4 this month. Hmm.. It’s ok. of course we don’t want lot of bugs. SO better give them more time to fix everything and give us the best. Thank You WordPress team.
I have been waiting for 2.4 but Ok. Thanks for informed us.
HNY.
Hey cool. I was looking forward to checkin out the new version, but if you have more tricks up your sleeves I won’t complain! I love my current installation – so I’m not in a total hurry to upgrade yet. When 2.5 comes out, I’ll be in line to get my very own fancy-schmancy copy!
Rock on, WordPress dev team!
Excellent – much as I love how WordPress gets new stuff out the door quickly – it’s been a real time drain trying to ‘stay current’ with new releases flying out so quickly with multiple sites in production using it. I welcome the break to catch my breath (and update a few sites STILL running 2.2 🙂 )
No theme releases these days?
Srik: Jim is on “vacation” for the holidays. The theme and plugin releases will be back online shortly. Thanks for your patience.
Ah, excellent! I really enjoy hearing when a team of developers such a the ones for WordPress make a common sense decision like that. Good on ya! The same was done for tagging which I was also impressed by. Also shows you pay attention to your users, ay?
I’ll definitely be looking forward to the March release. By what I hear it should be really something. Hey, and March is my birthday…oh…wait, almost fifty. Never mind that then. Just get it out before the 27th okay? 🙂
good sounds, i hope next version have amazing innovation 😉
Good, maybe there’s still time to get shared user tables working a bit better in 2.5! 🙂
I can’t wait for the next release, but why not just call it 2.4 as it can just confuse things…?
oh poo
Thanks Mark, just wondering…
@Srik
You can still stay current with new releases (themes and plugins) by watching the News section of this fine blog.
If there isn’t going to be a 2.4, why not just call 2.5, 2.4? I mean, if 2.4 isn’t being released, then there really never was a 2.4 to begin with, right? Why skip a number just because it’s being delayed? If versions are tied to timing, why not just call it version 2008.3?
Lame.
I don’t know pnaw10.com, but I have seen developers do that many times before. From what I gather, they do it for moral reasons, to give them an excuse for delaying a posted schedule. I agree, don’t make any difference to me either. I’d wait a year for a new major release, I don’t care, I like wordpress how it is, but not everyone is like that I guess, some people get pretty irate about stuff like that, keeping on schedule and everything. For something thats free, I say, who cares. hehe
The only thing I wish to see in a future WordPress release, is a better way of upgrading to a new version. Subversion, I must say, royally sucks, and does not work, and nobody ever posts a simple “howto” on how to do it anywhere, so the subversion stuff, I don’t know why they even promote that. I never was successful at getting that to work, even on a dedicated server (shrugs) much of less shared providers that don’t allow that.
right now, the easiest way to upgrade wordpress is thru Fantastico, but Fantastico skips minor releases, which I think is a major security risk, but anyway wordpress needs some sort of “web automated” method also. Even if it askes for the FTP information on the web screen somehow, that is easier for alot of people then using FTP to upgrade
@bubazoo
I agree with the need for an easier way to upgrade. I have found that the majority of bloggers who “do-it-themselves” these days rather dread doing any sort of upgrade. This is good in a way as it indicates there are more “non-tech” minded folks going over to a custom WordPress install but it also shows an increasing need for a much easier upgrade process that could be done right from the Admin.
A good example of this type of feature is provided by the “WordPress Automatic Upgrades Plugin” by Keith Dsouza. Beats the you know what out of a manual upgrade any day, accessed from within the Admin itself and offers a step-by-step method or fully automated method of upgrading. A lot is dependent on the host of course but with hosts that don’t crank down on permissions, the plugin works fine. Most users of the plugin that I’ve encountered don’t have a problem with it. I suppose the functions of this plugin could be incorporated into WordPress but would adding more to the core functions already there be preferable over adding the functions via a plugin is the big question here (as always when it comes to new functionality).
Wow wee, really lighting up the comments and links on this post. Perhaps I should review a couple of plugins that deal with upgrading WordPress?