Howdy, folks! Another week, another beta. Since we released Beta 1 last week, we’ve committed more than 60 bug fixes and feature adjustments based on testing and feedback. If you’ve been testing Beta 1, please update to Beta 2 to make sure things are still working for you. If you are a theme or plugin author and have not yet started testing your code against the 3.4 beta, now’s the perfect time to start. And as always, if you find any bugs, let us know! Full details on testing and bug reporting can be found in last week’s Beta 1 post.

Download WordPress 3.4 Beta 2

Original post by Jane Wells

WordPress 3.4 is ready for beta testers!

As always, this is software still in development and we don’t recommend that you run it on a production site — set up a test site just to play with the new version. If you break it (find a bug), please report it, and if you’re a developer, try to help us fix it.

If all goes well, we hope to release WordPress 3.4 in May. The more help we get with testing and fixing bugs, the sooner we will be able to release the final version. If you want to be a beta tester, you should check out the Codex article on how to report bugs.

Here’s some of what’s new:

• Theme Customizer with Previewer
• Flexible Custom Header Sizes
• Selecting Custom Header and Background Images from Media Library
• Better experience searching for and choosing a theme

And some of the under-the-hood changes:

• New XML-RPC API for external and mobile applications
• New API for registering theme support for custom headers and backgrounds
• Performance improvements to WP_Query by splitting the query (Please test!)
• Internationalization improvements (improved performance and locale support)
• Performance and API improvements when working with lists of installed themes
• Support for installing child themes from the WordPress Themes Directory

Remember, if you find something you think is a bug, report it! You can bring it up in the alpha/beta forum, you can email it to the wp-testers list, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac. (We recommend starting in the forum or on the mailing list.)

Theme and plugin authors, if you haven’t been following the 3.4 development cycle, please start now so that you can update your themes and plugins to be compatible with the newest version of WordPress.

Download WordPress 3.4 Beta 1

Original post by Jane Wells

WordPress.org is officially joining the protest against Senate Bill 968: the Protect IP Act that is coming before the U.S. Senate next week. As I wrote in my post a week ago, if this bill is passed it will jeopardize internet freedom and shift the power of the independent web into the hands of corporations. We must stop it.

On January 18, 2012 many sites around the web — from small personal blogs to internet institutions like Mozilla, Wikipedia, reddit, and I Can Has Cheezburger? – will be going dark in protest and to drive their visitors to sites like americancensorship.org to take action and help fight the passage of the Protect IP Act. So will WordPress.org.

If you want to join the protest by blacking out your WordPress site or applying a ribbon, there is now a variety of blackout plugins in the WordPress.org plugins directory. While joining the protest in this manner is laudable, please don’t forget to also make those phone calls to U.S. Senators — they’re the ones with the voting power.

• Get a protest plugin
• Take action at americancensorship.org

Original post by Jane Wells

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. We’ve published a number of posts on the development blog that explain important things you need to know as you prepare for WordPress 3.3. Please review this information immediately if you have not done so already.

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. Or, if you’re comfortable writing a reproducible bug report, file one on WordPress Trac. Known issues that crop up will be listed here, but let’s all keep our fingers crossed for a quiet Sunday so we can get these new features into your hands early next week!

To test WordPress 3.3, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip).

Original post by Jane Wells

It’s almost that time again, when the WordPress core development team gets together in person to review the year’s progress and talk about priorities for the coming year. Next week Matt Mullenweg, Mark Jaquith, Peter Westwood, Andrew Ozz, Andrew Nacin, Dion Hulse, Daryl Koopersmith, Jon Cave, and I will meet at Tybee Island, GA, the same location as the last meetup.

Last year we wanted to do a video town hall, but ran into technical and scheduling difficulties. This year we’re planning ahead, and will definitely make it happen. We’re currently taking questions, and will record a series of town hall-style videos where we answer your questions. Ask about the roadmap, code, community, contributing, WordCamps, meetups, themes, plugins, features, you name it. No topic (as long as it is about WordPress) is off limits, and we’ll do our best to answer as many questions as we can while we are together. The videos will be posted to this blog and archived at WordPress.tv.

Last year the people who were in attendance also posted pictures and updates to Twitter using the #wptybee tag. We’ll use the same tag this year, so if you’re interested in following along, add it to your Twitter client as a search.

What do you want to know from us? Ask away!

Original post by Jane Wells

The march toward 3.3 continues!

With all our major tickets closed, we are very close to a release candidate. In Beta 4 we’ve fixed a bunch of bugs, cleaned up the UI, added real text in some of the screens that still had placeholder text in Beta 3 (post-update screen, the Dashboard welcome area, new feature pointers), and generally tightened things up. We updated to jQuery 1.7.1 and addressed a LOT of bugs.

If you are a plugin or theme developer (or distributor), please test against Beta 4 to ensure there are no issues.

If you find any problems, please report them as usual. Many thanks!

Thought 3 was the last?
Ha ha! Beta 4 is here –
Better get testing!

Download WordPress 3.3 Beta 4

Original post by Jane Wells

We need your opinion! One of the features we’re adding to WordPress 3.3 (currently in beta 3) is intended to reduce widget pain. Say you’re using Theme A and you have a handful of widgets set up. You switch to Theme B, and it has different widget areas, so you add/remove/edit your widgets. Then you realize that you hate Theme B. “This theme doesn’t represent my innermost soul!” you cry to the heavens. You switch back to Theme A, but because it had different widget areas, now your widgets are messed up. Argh, right? Not for long!

Imagine being able to change themes and modify widgets as needed, and if you decided to go back to your old theme, it would return your widgets to how they were the last time you had that theme activated.  Sounds good, yeah? The problem we’re facing is deciding how long to save the old widget configuration, since there are so many potential workflows. If you changed From Theme A to Theme B and added more widgets over the next few weeks, if you switched back to Theme A after a month, would you still expect it to go back to the widgets from a month ago? At what point does it go from handy timesaver to unexpected widget mangler?  What do you think?

View This Poll

Original post by Jane Wells

Today is the eleventh day of the eleventh month of the (20)eleventh year, and in several parts of the world, it is a holiday related to war. In the U.S., where I live, it is Veterans Day, which honors military veterans. In much of Europe, today is Armistice Day or Remembrance Day, commemorating the armistice signed at the “eleventh hour of the eleventh day of the eleventh month” of 1918 that ended the fighting on the Western Front in World War I.

Whether serving in the military, living in an area of unrest or attack, having friends or family in the fray, or just being human enough to think war sucks (there’s really no gentler way to say that, is there?), war impacts most people in the world today.

The mission of WordPress is to democratize publishing. Sometimes we’re fortunate enough for that to mean providing a platform for communication that helps people work toward peace in their communities and around the world. Sometimes it means providing a platform for keeping people informed and aware of the things that are happening around the world, including the horror of wars and revolutions.

At WordCamp San Francisco in August, one of the most popular and well-respected sessions was led by Teru Kuwayama of Basetrack.org. On this day of remembrance, I thought it would be good to share the video of his presentation. Not only is it a very cool example of how WordPress can be used in unexpected ways (this is not your father’s Oldsmobile usual blog), it’s a reminder of how much work still needs to be done to move from war to peace. So here is Taking WordPress to War: Basetrack.org. Peace out, yo.

Original post by Jane Wells

Testers, Beta 3 is now available! You know the drill: use a test install, see what you can break, and report any bugs you find. There have been 200 commits since Beta 2, but at this point, betas are not adding new features — it’s all about fixing bugs, making things a little prettier, and editing text strings.

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.

These silly haikus –
With so many releases,
I run out of words.

Download WordPress 3.3 Beta 3 now.

Original post by Jane Wells

The annual WordPress conference, WordCamp San Francisco, starts in fewer than 8 hours. The sold out event — three full days of programming for bloggers, developers, theme designers, and professional WordPress users — will be shared with more than 1,000 ticket holders from near and far. If you are one of the many people who wanted to come but couldn’t swing the time off or travel expenses, you should check out the livestream tickets that are for sale. You can even get a conference t-shirt to commemorate your “virtual” participation.

Speakers include members of the WordPress core development team, leaders of WordPress-based businesses, hobbyists, and everything in between. Take a look at the schedules for Friday, Saturday, and Sunday, and if you see something that sounds interesting (how could you not?), buy a livestream ticket. The stream will start at 16:00 UTC on Friday, August 12.

Viewing Parties

Celebrate your own local WordPress community by calling together some friends and having a livestream viewing party. In the case of regular WordPress meetup groups, if you do a viewing party we will have a process after #WCSF is over whereby attendees will be eligible to buy conference shirts if their meetup group organizer confirms viewing party attendance.

Videos from all the recorded sessions will be posted for free on WordPress.tv within a couple of weeks, but watching the livestream allows you to support WordCamp while providing instant gratification. And let’s face it: the best part is that you’ll know what the heck people are talking about on Twitter using the hashtag #wcsf.

Original post by Jane Wells