You might have thought the release of 3.3 RC2 was the last before the final release this cycle. If you did you’d be wrong, since I bring you news of Release Candidate 3 announced over the weekend. Jane Wells handled the announcement, and let us know just how close we are to the final version of 3.3:
The third (and hopefully final!) release candidate for WordPress 3.3 is now available. Since RC2, we’ve done a handful of last-minute tweaks and bugfixes that we felt were necessary.
Our goal is to release version 3.3 early next week, so plugin and theme authors, this is your last pre-release chance to test your plugins and themes to find any compatibility issues before the final release.
If you want my guess, I’m predicting Tuesday or Wednesday. What’s your bet?
As uaual, if you’ve spotted a bug you can make it known in the Alpha/Beta section of the support forum or head on over to WordPress Trac and file the bug report there. You’re also reminded to check out the important things you’ll need to know, that are published on the development blog.
Normally when useful posts show up on the WordPress development blog I’d be here posting them for you. In this case core developer Andrew Nacin took care of that for me, which means I only have to post one link to his post. So you get awesome developer tips for 3.3, and I get to conserve some links. Win win.
It was just 6 days ago that WordPress 3.3 RC1 was released. Since then there’s been a handful of bugs fixed—then some more—and a few small tweaks to polish up the overall interface. Now we’re looking at RC2, just 32 commits later. Andrew Nacin made the announcement, and had to say:
As the first release candidate was well-received, we think we’re really close to a final release. Primarily, we’ve ensured that new toolbar (the admin bar in 3.2) has a consistent appearance across all browsers, and the API for developers is now final. You can check our bug tracker for the complete list of changes.
So if you’re looking to get your plugins and themes ready for when WordPress 3.3 drops, you’ll find your fair share of information on the development blog. I’d suggest you check it out, at the very least, there’s some live code examples you might find handy in the future.
If you spot a bug, you know the drill. Simply head on over to the alpha/beta section of the support forum and report your findings. Unless you’re
comfortable writing a reproducible bug report as Nacin points out, in which case you can write one out on WordPress Trac.
Are you prepped for the release of the new version yet?
The core team was up late last night specifically to push out Release Candidate 1 of WordPress 3.3. The milestone comes a bit later than was intended by the 3.3 Project Schedule, but it still puts the project in a position to release the final version by the end of 2011.
Normally I’d say you can read more about the RC1 status on WordPress.org, but as you might expect a late evening release tends to lead to shorter release posts. Still: we’re talking piping hot WordPress here, and it’s ready for another round of testing, if you’re willing.
Assuming you’ve been playing with 3.3 a bit already, share a thought or two in the comments.
Aaron Brazell, who recently stepped away from his role at WPEngine, has posted ten things you need to know about WordPress. He does these helpful feature overviews for every release.
WordPress 3.3 Beta 3 has been announced, which means local and test installs all over the planet should be clicking on to give this new one a go. You should test with your themes and plugins, particularly if you’re a developer of one that uses jQuery since this release includes jQuery 1.7. We’re not quite at the stage for a Release Candidate yet, but we’ll get there shortly.
In Jane Wells’ announcement she mentioned that there have been 200 commits made since beta 2. Now it’s all about bug fixing, not adding in any new features. Everything will just get a little prettier as more developers squash bugs and make fixes. She goes on to say:
As always, plugin and theme authors, PLEASE test your code against the beta so you can catch any incompatibilities now rather than after your users update their WordPress installation and find bugs for you. This time we really mean it, especially if your plugin uses jQuery. We’ve now updated to jQuery 1.7 in core, so please please pretty please check your plugins and themes against beta 3.
Even if you’re not a developer, why not try out your favourite plugins on a test install and let the developer know if you do encounter a problem? That will allow them to check things out before the official release of WordPress 3.3, which is still targeted for November.
Have you updated your test install to beta 3 and started the search for bugs? If you do find one – pesky little things – head on over to the alpha/beta section of the WordPress Forums to see if others are reporting the same thing, or ping the wp-testers mailing list if it’s worthwhile.
I know what you are thinking. Doesn’t it feel like WordPress 3.2 was just released? Well WordPress 3.3 beta 1 is already here, and while it’s not quite the final version it does meanthat we’re getting much closer!
WordPress Lead Developer Ryan Boren announced on the WordPress.org blog that the first beta is ready for testing. So it’s time to get out your flyswatters and be on the lookout for any bugs that need squashing.
- jQuery 1.6.4 and jQuery UI 1.8.16,
- the WordPress Editor API,
- refactoring of Quicktags,
- a new multi-file uploader, and
- some native WordPress function updates.
The addition of jQuery 1.6.4 and jQuery UI 1.8.16 includes the full UI, widgets, effects and everything! This makes it easier for plugins to use UI components that aren’t included in core.
The updated Editor API is for TinyMCE and Quicktags. It outputs all parts of both of the editors in the same way as the Add/Edit Post screens. Plugins can use the WordPress editor anywhere.
The WordPress 3.3 “feature freeze” is now in effect, which means no more features will be added to this particular release of WordPress. The week before complete feature freeze took effect only the lead developers could commit new features to 3.3, but now that period is over as well. If your favorite feature hasn’t been reviewed, with a patch ready to go, you can expect it to be bumped to the 3.4 development cycle.
WordPress User Experience Lead Jane Wells announced the onset of the freeze on the WordPress Development blog, which came a week later than intended:
We were supposed to have freeze a week ago for everything being worked on by contributors, then a week for the core team to do a scrub and commit or punt all those enhancement/feature request tickets as well as finishing up their own 3.3 feature dev before full on freeze today. We gave contributors some extra time at last week’s dev chat as there were some features not quite ready (HTML emails, Settings CSS, etc). Sadly, the extra time didn’t lead to commits, and now we’re just a week behind. So!
The feature freeze taking place now is right in line with wrapping and releasing 3.3 by November 29, the current target date as per the 3.3 project schedule. The end of October should see the release of Release Candidate 1, followed by the full launch at the end of November.
The next big target is a beta release and code freeze on October 5. After the first beta all work will be focused entirely on bug fixes to ensure a stable release.
Assuming the schedule is kept, 3.3 will be the third major release of WordPress in 2011: first 3.1 Reinhardt in February, then 3.2 Gershwin in July, and finally the currently unnamed 3.3 release in November. Remember that you can track our coverage of the WordPress 3.3 development cycle as well.
You be the judge: is it time to start proposing jazz musicians to nickname this release cycle?
WordPress 3.3 isn’t that far away when you think about it, but really there’s still lots to do before it’s ready for release. A new addition, Admin Pointers, was committed within the past few days. Not long after the team over at Theme.fm decided to experiment and see just what could be done with this yet-to-be-released feature.