Congratulations all contributors to BuddyPress 2.6! For those who attend our dev meetings regularly, please note that next week’s scheduled meeting — 29th June — is cancelled to give everyone a chance to relax. It’s quite probable that some members of the team will be on Slack then anyway, so we’d love to have a casual chat if you happen to be around.
The dev chat scheduled for 6th July is on, and it will be used to discuss any problems that have been found since release of 2.6, and to discuss ideas for BuddyPress 2.7 and ways to help contribute to it.
Read more about it here https://buddypress.org/2016/06/buddypress-2-6-0/
Let’s all thank @dcavins our release lead for this delicious 2.6 version.
Many thanks to all our contributors ❤️
abweb, Boone B Gorges (boonebgorges), Brandon Allen (thebrandonallen), chherbst, danbrellis, David Cavins (dcavins), Dennis (wpdennis), emrikol, Fee (wdfee), Garrett Hyder (garrett-eclipse), Gary Pendergast (pento), George Mamadashvili (Mamaduka), Henry Wright (henry.wright), Hugo (hnla), John James Jacoby (johnjamesjacoby), Klaus (kmbdeamorg), OC2PS (sooskriszta), lakrisgubben, Laurens Offereins (Offereins), mahadri, Mathieu Viet (imath), mercime, Michael Beckwith (tw2113), mmcachran, modemlooper, Nick Momrik (nickmomrik), OakCreative, oksankaa, Paul Gibbs (DJPaul), Rami Yushuvaev (ramiy), r-a-y, rekmla, r0z, Sergey Biryukov (SergeyBiryukov), singhleo, Slava UA (slaffik), Stephen Edgar (netweb), tharsheblows, VibeThemes, vortfu, WeddyWood, w3dzign.
BuddyPress RC 1
@dcavins packaged and released BuddyPress 2.6.0 RC 1 (string freeze) last Wednesday, June 15, 2016.
* Developers: Please test your BP plugins and themes with our new features this dev cycle
* Translators: We need translators for BuddyPress. If you’re interested in contributing, @danbp has written a topic about how you can get involved.
RC 1 Release Preparation
We discussed two tickets remaining in trac: moving stylesheet of activity embed to to bp-legacy’s
/css/ folder (#7123 fixed.) and the Welcome Screen for 2.6 (#7108 fixed).
* Thanks to @im4th for preparing the video demonstrating BP’s new Activity Embed feature on our Welcome Screen.
* Thanks to @djpaulgibbs and @jerrysarcastic for facilitating the transfer of the video to WordPress.tv.
* And thanks @dcavins, @rayisme, and @hnla for improving the text of the Welcome Screen.
New Codex articles for BP 2.6
Thanks to @rayisme for publishing the following articles:
* Activity Embeds
* Group Types API
Improving Management of Trac Tickets
@djpaulgibbs will be implementing some changes to Trac over this weekend per his post here at bpdevel. @dcavins reminded all to comment on @offerein’s suggestions about BP trac ticket categories and focuses.
Slack log: https://wordpress.slack.com/archives/buddypress/p1466017239000114
BuddyPress 2.6.0 Release Candidate 1 is now available for testing. Please let us know of any issues via our issues tracker or on the BuddyPress support forums.
Thanks in advance for your help!
- Release Candidate 1 (string freeze): June 15, 2016
- 2.6.0 release: June 22, 2016
- There are currently 106 tickets in queue (Closed: 103. Open: 3.)
A new API to manage single items navigation (#6534) Issue on backward compatibility with groups navigation. Update: @boonebgorges has committed fix to trunk.
Activity link moderation doesn’t output useful error message to end users (#6719) @rayisme will be making a string change. Update: @rayisme has committed the fix to trunk.
Welcome Screen for 2.6.0 (#7108)
* Activity embeds will be the main feature of the About page. A short video will be embedded for WP 4.5+ installations and an image for installations less than WP 4.5. @im4th was volunteered to make the video. Update: @im4th has uploaded a patch.
* Other items to be featured included the new Group Types API and Custom Users Front Page
* In the midst of testing the Activity embeds feature for the About page, @tw2113 found a bug. Update: @im4th created a new ticket and he and @rayisme have uploaded patches to fix the issue.
* In addition, the WP icon was seen in BuddyPress.org’s activity embeds. @im4th pointed out that a ready-to-use BuddyPress icon exists on the “official fonts and logos” page. Update: @djpaulgibbs has uploaded the icon.
* “Under the Hood” section: New API to manage single items (Member or Group) navigation, various caching improvements, among other items.
Slack log: https://wordpress.slack.com/archives/buddypress/p1465412393000100
I’ve been reviewing how we manage trac tickets to try to improve how we manage and prioritise feature requests and suggestions. We have many great ideas in our Future Release milestone, but all too-often that’s become the place where great ideas go to die. At time of writing, the milestone contains nearly 700 tickets, and not even I know what’s good in there, or even what was once good but now redundant.
Our current workflow is: new ticket -> [Awaiting Review] -> [Under Consideration] -> [Future Release] or [Release Milestone] or closed ticket.
“Under Consideration” is where new suggestions live while we evaluate them and gather further feedback and comment. This is a relatively recent addition in the last couple of years, and it’s helped seperate tickets we haven’t looked at yet (“Awaiting Review”) to those we are looking at.
I propose we should try tweaking how we approach the “Future Release” milestone so we gain better understanding and awareness of vetted suggestions and bug reports, which in turn will help existing and new contributors find exciting tasks to work on. Et voilà!
- At the top of the pyramid, we have the two next release milestones (major and minor releases) which will work the same as they do today.
- “Up Next” is a new milestone containing important or strategic tickets that our regular contributors have expressed in working on within the next two releases.
- “Maybe Later” is a new milestone containing tickets that our regular contributors have decided that we have significant interest in working on, or are of a strategic importance, but less so than those in “Up Next”.
- “Awaiting Contributions” is a new milestone. It contains tickets that our regular contributors have decided would be valuable enhancements for BuddyPress, but which are unlikely to be worked on by those regular contributors for the forseeable future — because they are less important than those in the other milestones.
- This is pyramid-shaped on purpose. The milestones at the bottom should always contain more tickets than those at the top.
If this idea has support, we’ll have to spend alot of time reviewing the entire Future Release milestone, which is a great opportunity to close any tickets that are now irrelevant for some reason. The “Future Release” name itself would no longer be used to avoid confusion.
I would be very happy to hear your feedback on the proposed milestone changes (would they work? are they solving the right problem?).
@im4th shared how he used BuddyPress and BP plugins for his company’s intranet at WordCamp Antwerp. Read all about it at https://buddypress.org/2016/06/buddypress-at-wordcamp-antwerp/