It’s Wednesday! It’s also 14 days before feature development ends for BuddyPress 1.8, so let’s recap where we’re all at!
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
Wednesday updates! How’s your BuddyPress gone this week, feature leads?
I’m going to start this week’s updates with mine.
UI Refresh (http://buddypress.trac.wordpress.org/ticket/4953):
New message styling.
@hugo has some more ‘detheming’ that was missed he’s going to commit.
New templates (http://buddypress.trac.wordpress.org/ticket/4952):
I added some mockups: http://buddypress.trac.wordpress.org/ticket/4952#comment:7
I also updated the dropmark board to show the wireframes Turtleshell was using (more as a record)
This week we move into refining and commenting.
Let’s try something new; each Wednesday, would people leading on a headline feature for 1.8 please publish a brief progress update to the weekly update post.
Doesn’t matter when on Wednesday, as long as it’s still Wednesday wherever you are
I’m hoping this will increase visibility of things that are in development, as it’s hard for someone not going to the dev chats or reading the IRC logs to find out the current status of a particular feature, and in turn help us keep 1.8 on schedule.
I’ll post mine later to kick things off!
BP 1.7.1 is now available. View the blog post for more info http://buddypress.org/2013/04/buddypress-1-7-1/
At yesterday’s dev chat, we made some broad decisions about scope, and some specific decisions about timelines, for the BuddyPress 1.8 release cycle.
The major improvements slated for BP 1.8, and the team members who’ve committed to lead them up:
meta_querysupport for the main template loops. See #3521 and Eric Lewis’s preliminary patch for the activity component. (Boone)
- Migrating to the WP Rewrite API. See #4954. (John)
- Template hierarchy for BP template parts. See #4639. (Ray)
- Automatic download and update of language packs. See #4857. (Paul)
- General tidying of BP UI styling. See #4953. (Tammie)
- New template pack. See #4952. (Tammie)
- Miscellaneous improvements to
BP_Group_Extension. See #4955. (Boone)
- Convert group member queries to
BP_User_Query. See #4482. (Boone)
A number of these items (especially #4482 and #4952) are somewhat questionable for 1.8, due to their size and to our tight deadlines. The team may decide partway into the cycle to punt them.
In addition to the major items listed above, the 1.8 milestone contains a number of smaller enhancements, which can be rolled into the release if folks step up to the plate with patches, testing, and feedback.
We’re experimenting with a short release cycle: six weeks for feature development, and six weeks for testing. The following dates are of particular interest:
- June 5, 2013 – End of feature development. Beyond this date, nothing gets committed that is not either a bug with a new feature, or a regression from 1.7.x. Any major features from the list above that are not commit-ready by this date will not be included in BP 1.8. At the dev meeting on June 5, the team will make decisions about borderline cases – features that are partially implemented. We plan to release BP 1.8 beta1 in the days immediately following June 5.
- July 17, 2013 – BP 1.8 final release
The timetable is, by design, compressed. As part of our experiment in a shorter dev cycle, we’re going to hold to this proposed schedule as strictly as possible.
Interested in contributing to BuddyPress during the 1.8 dev cycle? The more the merrier! Join us in our weekly dev chats (see sidebar for details), visit one of the tickets listed above, or dip your toe into the 1.8 milestone. Core devs are generally lingering in freenode #buddypress-dev, so please stop by if you’re looking for a place to start.
At next week’s dev meeting (April 24 – see the sidebar of this blog for time details), we’ll be discussing the scope and schedule for the BuddyPress 1.8 release. The tentative plan is to have a short release cycle – 12 weeks from the beginning of development to the final release. The core team is asking that interested parties leave suggestions about what to include in 1.8 in the comments below, for discussion at the Apr 24 chat. And if (especially if) you can commit to doing significant development/testing for a given feature, you should mention that too.
For reference, here’s what’s already (tentatively) in the 1.8 milestone on Trac: https://buddypress.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&milestone=1.8&groupdesc=1&group=priority&col=id&col=summary&col=milestone&col=status&col=type&col=priority&col=component&order=priority See something on that list you want to help with? Feel free to mention that below, too.
As promised, I’ve started a codex page that explains how to take advantage of BuddyPress’s new automated testing suite when writing unit tests for your own BP plugins. http://codex.buddypress.org/developer/automated-testing/writing-automated-tests-for-buddypress-dependent-plugins/ has lots of details and a working example, but the summary is: require
buddypress/tests/includes/loader.php before your own plugin to make sure that BP gets installed and initialized, and require
buddypress/tests/includes/testcase.php for access to BP’s testcase class and factories.
Questions or comments? Please leave them below.
Unfortunately, BuddyPress’ application to be a mentoring organisation for GSoC 2013 was rejected. We’d like to thank everyone who helped put together the application and ideas pages, and those who volunteered to be a mentor. However, WordPress got in!
If those people would still like to mentor a WordPress project, or you’re a student and you’d like to work on a BuddyPress project, then I’d encourage you to applying as a mentoring or student to the WordPress project. Check out make/core for details.
Over the last few months, Paul and I have been building a framework for writing unit and integration tests for BuddyPress. As of tonight, the BuddyPress automated test suite is part of BuddyPress core. (See r6905-6908)
I’ve started a Codex page about our tests: http://codex.buddypress.org/developer/automated-testing/. The BP tests are modeled after the WordPress suite; you can read much more about how WordPress tests work at https://make.wordpress.org/core/handbook/automated-testing/.
If you are a BuddyPress plugin developer, or if you contribute to BuddyPress itself, you’re highly encouraged to use, and contribute to, our test suite. The test coverage right now is very, very sparse, but we hope that it will improve as we fix bugs and refactor various parts of the codebase.
An exciting feature of the BP test suite is that it allows dependent plugins to write tests that invoke
BP_UnitTestCase and other BP-specific tools. I will write more about this feature, including examples from my own plugins, in the upcoming days.
The testcases are located in the
tests/testcases subdirectory of BP’s plugin folder. Bug reports and enhancement requests should be reported to BP Trac.