Recent Updates

Unknown's avatar Renato Alves 8:51 pm on October 6, 2026
Tags:   

BuddyPress 15.0: updated release schedule

Hi! It’s been a while. =)

I want to share the updated plan for BuddyPress 15.0.0. We are targeting 19 January 2027 for the final release.

If you have been following this release, you know it has taken longer than we initially planned. I’ll talk about that below. But first, the dates, and what we hope to have ready along the way.

Release schedule

DateMilestone
1 December 2026Preparation checkpoint: review documentation drafts, the changelog, and related plugin compatibility work.
8 December 2026Target publication date for the REST API V2 introduction, deprecated-function notice, and standalone BP REST API plugin guidance.
15 December 2026BuddyPress 15.0.0-beta1 — feature freeze and community testing.
5 January 2027BuddyPress 15.0.0-rc1 — release candidate and string freeze.
18 January 2027Release dry run: check packages, installation, upgrades, and release materials.
19 January 2027BuddyPress 15.0.0 final, subject to testing results.

The plan is one beta and one release candidate. That’s the starting point, not a limit. If testing shows we need another beta or RC, we will publish one.

Why January? WordPress 7.2 is currently scheduled for 8–10 December 2026. This gives us time to test BuddyPress against its stable release, without putting the final BuddyPress release in the middle of the year-end holidays.

We have allowed three weeks between Beta 1 and RC1 because of those holidays, then two weeks between RC1 and the final release.

Documentation and related plugins

REST API V2 is an important part of this release. I want developers to have a chance to understand the changes before trying the beta. Our goal is to publish its introduction one week before Beta 1, along with the a blog post with the functions or/and features we are deprecating, and guidance for users of the standalone BP REST API plugin.

These posts will cover the changes, replacements, and migration considerations for existing integrations.

But I also want to be clear about what happens if they are not ready: unfinished documentation will not block the release. The publication dates above are goals. If we miss them, we will share what is available and continue publishing the remaining guidance as it is ready. Beta 1 does not depend on those posts being published a week earlier. Even though we will do our best to get them ready in time. 🙂

Related tools and plugins need attention too. That includes wp-cli-buddypress and other integrations maintained by the team. We will test their compatibility and aim to make any required updates available before the final BuddyPress release.

About the delays

BuddyPress 15.0 has taken longer than originally planned. We have moved release dates before, and I know that makes it harder to plan your own updates. Thank you for sticking with us.

I recently read the Preact 11 announcement. Their roadmap ticket opened more than six years earlier, while work continued on Preact X. Different project, different timeline. But it was a reminder that a major release can take a long time without development stopping.

That is not a reason to leave you guessing about BuddyPress, though. My goal with this post is to make the plan clear: what we are aiming for, what still needs testing, and what could change.

These dates are targets, not a guarantee. If WordPress 7.2 moves or testing uncovers release-blocking issues, we will reassess the affected dates. I would rather allow time to test a fix than rush it into a final release to meet the calendar.

If the schedule changes, we will post an update here explaining why and sharing the revised dates. Documentation may follow later, but release-blocking bugs still need to be fixed.

A note about BP Dev-Chat

If you follow our BP Dev-Chat summaries, you may also be wondering about the meetings. BP Dev-Chat is suspended for the time being. When we bring it back, the plan is to meet monthly. We will announce the return date and meeting time here.

The BP Docs-Chat meetings were already suspended in August 2025. Documentation work continues as time allows. Pausing the meetings does not mean that work has stopped.

Help us test

Once Beta 1 is available, please give it a try on a development or staging site—not your production site. If you maintain a BuddyPress plugin or theme, this is a good time to check your integrations, REST API usage, and deprecated-function calls.

You can follow the remaining work in the BuddyPress 15.0 milestone and report bugs on BuddyPress Trac.

You do not need to write code to help. Testing an upgrade, reviewing a documentation draft, or reporting a compatibility issue all help us understand what still needs attention.

That’s the plan for now. I’m looking forward to getting this release into your hands, and hearing how it works with the communities you are building.

#15-0-0

Unknown's avatar emaralive 2:06 pm on July 30, 2026
Tags: , ,   

BuddyPress 14.5.2, 12.7.2 & 11.6.2 are available

These are security and maintenance releases. Please upgrade, accordingly 🙏.

Version 14.5.2

🍕

#maintenance, #release, #security

Unknown's avatar emaralive 12:40 pm on July 8, 2026
Tags: , ,   

BuddyPress 14.5.0, 12.7.0 & 11.6.0 are available

These are security and maintenance releases. Please upgrade, accordingly 🙏.

BuddyPress 14.5, 12.7, 11.6

🍕

#maintenance, #release, #security

Unknown's avatar emaralive 7:56 pm on September 24, 2025  

BuddyPress 14.4.0, 12.6.0 & 11.5.2 are available

These are security releases. Please upgrade, accordingly 🙏.

BuddyPress 14.4.0, 12.6.0 & 11.5.1 Maintenance and Security Releases

🍕

Unknown's avatar emaralive 8:53 pm on August 17, 2025  

Documentation (BP Docs-Chat) Team Meetings are Suspended

Due to other priorities, the Documentation (BP Docs-Chat) team meetings are suspended until further notice. In the meantime, documentation efforts will continue when time is available.

Unknown's avatar emaralive 6:21 pm on August 4, 2025
Tags: , ,   

BP Docs-Chat Summary July 23, 2025

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

Summary: There was very little to report due to @emaralive was still ramping up on the learning curve for the Docusauras tool. Additionally, @emaralive was the only one in real-time attendance.

1️⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 11:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

@emaralive reported that he was still digesting the documentation provided by the tool maker (Docusaurus).

Phase 2 feasibility studies status

  • In progress:
  • To Do:
  • Completed:
    • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3️⃣ Open Floor:

There were no conversations nor comments to report for this agenda item.

Next Docs-Chat

NOTE: The docs-chat meeting that was scheduled for August 6, 2025 is cancelled due to a conflict in schedule for @emaralive.

Our next documentation meeting will, tentatively, happen on August 20, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 1:19 pm on July 22, 2025
Tags: , ,   

BP Docs-Chat Agenda July 23, 2025

Hi!

Our next documentation meeting will happen on July 23, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1️⃣ BP Documentation tracker status.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 11

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

  • General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

Phase 2 feasibility studies status

  • In progress ❗ :
  • To Do:
  • Completed ⭐ :
    • Woocommerce REST API documentation, based on Slate – proposed here – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3️⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.

#agenda, #docs-chat, #documentation

Unknown's avatar emaralive 9:59 pm on July 21, 2025
Tags: , ,   

BP Docs-Chat Summary July 9, 2025

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1️⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 10:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

The conversation was basically a first look at the Docusaurus  tool and based on the implementation by the WordPress (WP) Playground team, this tool looks like it might be a nice fit for the 3 BuddyPress (BP) handbooks (User, Developer & Contributor). At this time, the tool had not been installed (locally) by @emaralive and he had indicated that he had queued up a couple of the online demos that were provided by the tool makers.

A main feature is SPA (Single Page Application); Internationalization (i18n) is another feature of which @rollybueno (async) indicated that he had translated documents for the WP Playground project (see Translation: Tagalog (Filipino) #2336).

@dcavins indicated “[t]he result is screaming fast to use” which the tool makers claim:

Lightning-fast. Docusaurus v2+ follows the PRPL Pattern that makes sure your content loads blazing fast.

Phase 2 feasibility studies status

  • In progress:
  • To Do:
  • Completed:
    • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3️⃣ Open Floor:

This agenda item was forgone due to an interruption in conversations caused by other pressing matters.

Next Docs-Chat

Our next documentation meeting will happen on July 23, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 8:01 pm on July 7, 2025
Tags: , ,   

BP Docs-Chat Agenda July 9, 2025

Hi!

Our next documentation meeting will happen on July 9, 2025, at 19:00 UTC in #BuddyPress. Here’s our agenda:

1️⃣ BP Documentation tracker status.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 10

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

  • General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

Phase 2 feasibility studies status

  • In progress ❗ :
  • To Do:
  • Completed ⭐ :
    • Woocommerce REST API documentation, based on Slate – proposed here – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

3️⃣ Open Floor

If you have specific or additional points to discuss, please do so in the comments section of this post.

#agenda, #docs-chat, #documentation

Unknown's avatar emaralive 7:03 pm on July 7, 2025
Tags: , ,   

BP Docs-Chat Summary June 25, 2025

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1️⃣ BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 9:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 1st feasibility study – Slate Docs

There were a couple of tests that were failing while deploying to the experimental repository (bp-rest-api-docs) that were related to Ruby versions 2.6 & 2.7. These failures appear to be attributed to upgrading the Bundler version to 2.5.3 which is currently compatible with Ruby version 3.x and not prior versions. Most likely, the testing for Ruby versions of 2.6 & 2.7 should be removed, given that the dependencies have been upgraded to be compatible with Ruby version 3.x.

The Slate tool analysis is basically complete, a documented report will be forthcoming, when time is available.

Phase 2 feasibility studies status

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

3️⃣ Open Floor:

There was a support forum topic, BuddyPress plugin not tested with my WP version, which brought to light that the latest version (14.3.4) of BuddyPress is only compatible up to WordPress 6.7.2. There was some discussion on how to handle the next upgrade, however the date for release is still yet to be proposed/determined due to not having a list of bug fixes, etc. that would be included within this next release.

Another topic of interest was an issue with fonts as rendered by various browsers and operating systems. an example is a reply to a support forum topic, cant find all the buddypress widgets, whereby some of the text should have rendered as bold. For example, @emaralive indicated that for Chrome based browsers on a Linux 64 bit distro, what should have been bold text does not appear as bold, however, @dcavins indicated that on a Mac with Firefox and Vivaldi the bold text is rendered as such.

Next Docs-Chat

Our next documentation meeting will happen on July 9, 2025 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary