Published on July 29th, 2011 by John James Jacoby
Wait… 1.5? What happened to 1.3? Or 1.4 for that matter?
You see… BuddyPress 1.2 was released on February 16, 2010. We’ve shipped 9 point releases since then, but it’s been over 17 months since a major release of BuddyPress has come through the tubes.
We do our best to mirror the WordPress development cycles as closely as possible – maybe a little too closely. Back in 2004, WordPress went through a growth spurt of its own, going 9 months between major releases (also between versions 1.2 and 1.5) so we are doing the same, and skipping ahead to 1.5 ourselves.
Here are the stats we’re using to justify the version inflation:
- 792 tickets closed
- 494 confirmed bug fixes
- 2,161 total code changes since 1.2 was released
The similarities between BuddyPress and WordPress development symbolize the nature of developing something totally new and exciting, so we think it’s fitting to bump our version number in a similar fashion.
Because of the volume of changes internally, we’re packaging up a developer beta so plugin authors have time to review our changes, report bugs, and give everyone a few weeks to tie up any loose ends that are left.
If you are a BuddyPress plugin author, now is your time to help us help you, and check out all the work that’s gone into making the next version of BuddyPress faster, more efficient, more secure, and easier to code against.
If you are a user or a designer, check out the changes to the BP Default theme. We’ve done our best to turn it into a theme you want to use, and have it still show off all the features too.
If you are neither (or both) of those things, you can help by documenting the codex. We’re trying to do our part by writing the phpDoc as we go, and if you can help move some of that into the codex, it helps everyone!
As always, please DO NOT run BuddyPress Beta software on your live production site. There are going to be quirks with existing plugins, and we will be updating code rapidly as bug reports come in. Install BuddyPress 1.5 on a local installation or a test site, and let us know if you find anything that isn’t working the way it should. We are hoping the beta period will only last a few weeks, with a release in August.
You can download BuddyPress 1.5 Beta 1 today, from the bottom of our Trac page. Happy Testing!
We’ll be doing some maintenance to BuddyPress.org this week, so don’t be alarmed if a few things aren’t working or go missing for a little while. We’ll try to make it as painless as possible, and we promise it will be worth it in the end. 🙂
Available immediately is BuddyPress 1.2.9. This is a bug-fix release of the 1.2 branch to ensure full compatibility with WordPress 3.2. (Note: This does not use the new bbPress 2.0! We’re working on it!)
BuddyPress 1.2.9 includes fixes related to the new version of jQuery (1.6.1) that comes packaged with with WordPress 3.2. These changes affect the javascript and ajax behaviors in the bp-default theme. You can read more about them on the WordPress development blog. If your BuddyPress site runs bp-default (or a child theme of it) you’ll need to update to BuddyPress 1.2.9 immediately after updating to WordPress 3.2.
Questions? Let us know in the comments or in the support forums, and stay on the lookout for an early preview of BuddyPress 1.3 sometime in July!
Download BuddyPress 1.2.9 from WordPress Extend or BuddyPress.org.
I’ve just released version 1.1 of the BuddyPress Template Pack. BP Template Pack is a plugin that provides you with the necessary templates to make your existing WordPress theme BP-compatible. The plugin now provides templates that are 100% up-to-date with the latest stable release of BuddyPress, which means that users will get all of the features and AJAX niceties enjoyed by sites that use the bp-default theme.
Those upgrading from an older version of the BuddyPress Template Pack can replace their existing BP templates, using the “Reset” button at Dashboard > BP Compatibility. Keep in mind that you’ll need to delete the BP template folders from your active theme (activity, blogs, forums, groups, members, registration) – for purposes of safety, this is must be done manually via FTP. Remember to back up any changes that you’ve made to these template files before deleting.
EDIT: As r-a-y points out, it’s a very smart idea to *back up* or *rename* your existing template directories instead of simply deleting them. Test this on a development installation before you do anything in a production environment, if you can.
During the day of Monday, April 4, we will be taking BuddyPress.org down to perform some routine maintenance. This will effect profiles.wordpress.org as well. We’re not doing anything fancy yet, just updating some of the inner workings to pave the way for future updates and enhancements.
Our next item up for bid is BuddyPress 1.2.8, which includes a few small bug fixes to the 1.2 branch of code and is a highly recommended update if you are updating to WordPress 3.1.
This release backports a few important fixes from the currently in-development 1.3 version of BuddyPress to play nicely with the new and very much improved WordPress network administration interface. We’ve also updated the bundled version of bbPress from 1.0.2 to 1.0.3, which addresses a few issues that do not effect BuddyPress directly.
Every effort has been put into supporting both WordPress 3.0 and 3.1 with this release to make updating your sites as painless as possible, so this should be another worry-free update!
BuddyPress 1.2.7 has just been tagged, and is ready for download! This maintenance release fixes several problems, and is an important upgrade for all BuddyPress installations. Check out the details of the 1.2.7 release at the official changelog.
Before upgrading your BuddyPress installation, make sure to back up your data and files, and deactivate BuddyPress-dependent plugins. (Or, as I like to call it, BUD. Somehow I have a feeling that won’t catch on….)
The community of BuddyPress contributors continues to grow! Huge thanks and überprops go out to those who have contributed to this release cycle: andrewteg, bizybee, calvin_42, cnorris23, intimez, jond, ptahdunbar, r-a-y, swinton. If I missed your name, let me know in the comments below.
Enjoy BuddyPress 1.2.7!
Ready immediately is BuddyPress 1.2.6 which includes a number of important bug fixes to the 1.2 branch of code and is another highly recommended upgrade. As always, be sure to back-up your installations before upgrading, and deactivate any dependent plugins that you might have to ensure there are no conflicts or errors during the process.
This version improves WordPress 3.0 compatibility, makes some minor tweaks to the included theme, and fixes a total of 91 reported issues! Check out the BuddyPress release history for details on the important fixes in this release.
BuddyProps
With almost 100 bugs fixed and issues addressed in 1.2.6, you can bet we have some people to thank. Firstly, congrats and thanks again to Boone and Paul for all of their help and contributions. They are both huge assets to the BuddyPress project and Andy and I are really happy to have their continued support. Props go out to benfremer, cnorris23, dwenaus, erich73, francescolaffi, hempsworth, intimez, jeffsayre, kunalb, paulhastings0, r-a-y, wpmuguru, and everyone else that contributed. (If I missed you, slap me with a trout and leave a comment below.)
Paul, Boone, and I spent almost 3 full days together at WordCamp New York talking about what we’d like to focus on and what direction we’d like to see things go. This version of BuddyPress has been one of our longest development cycles to date since we’ve gone 1.0. By bringing on Paul and Boone we’re going to ramp up production and set our sights on the next major version somewhere around the end of 2010.
Have fun and thanks for using BuddyPress!
Today at WordCamp New York (about 30 minutes ago in fact) I had the privilege of introducing Boone B. Gorges and Paul Gibbs as new core committers to the BuddyPress project.
In recent months both Boone and Paul have been heavily involved in team meetings, forum moderation, and producing outstanding core code patches. If you spend any amount of time in our forums or in our development Trac, then you have definitely spent some time with them and know that this isn’t really a huge surprise. 🙂
You know what this means, right? Look forward to some more awesome stuff coming in the next few weeks from the BuddyPress team, the project as a whole, and stay tuned to this blog for more news coming soon!
Congrats gents!
The Open Source Awards is an annual online event held by Packt Publishing to distinguish excellence among Open Source projects.
Now in its fifth year, the Award (formerly known as the Open Source Content Management System (CMS) Award) is designed to encourage, support, recognize and reward not only CMSes but a wider range of Open Source projects.
This year BuddyPress has the honor of being a finalist in the “Most Promising Open Source Project” category, which is for all Open Source projects that made their debut within the past 2 years. We’re up against some stiff competition with LiveStreet CMS, Pimcore, Tomato CMS, and WolfCMS, so we’re asking for your support!
I’d be lying if I said I didn’t want or care about the $2,500 prize for winning our category. Andy would really like a sweet 3D-TV, and I could use a posh new living room set myself, but we decided donating the proceeds to the WordPress Foundation was probably the best way to use any cash winnings. 🙂
To help make voting worth your while, PacktPub is giving away free Amazon Kindles to random voters and nominees. If showing your BuddyPress pride isn’t enough, do it for the opportunity to score a free Kindle!
So click the banner below and be whisked away to Packt Pubs voting page, where you can [help Andy enjoy Jurassic Park like it was meant to be enjoyed] [help John take epic naps on a new comfy couch] help support BuddyPress and maybe win yourself a Kindle!
