This is a maintenance release, please upgrade 🙏.
🍕
This is a maintenance release, please upgrade 🙏.
🍕
Near the beginning of each development cycle, we reassess BuddyPress’s minimum required WP version. Our rough guidelines are as follows:
We reassessed it recently as part of #9051, and we will be raising the minimum version of WordPress and PHP required as follow:
As part of this update, we also streamlined our testing matrix. And we already have been testing using cache services like Redis and Memcache to identify any possible issues for users of those tools.
As part of this update, we also reviewed our recommendations to run BuddyPress, we recommend your host supports:
^ this is not the minimum requirements, but solely our recommended ones.
Hi!
Our next documentation meeting will happen on September 4, 2024, at 19:00 UTC in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss, please share them in the comments area of this post.
The stats – 53%, which is an increase of 5 (five) percentage points – 48% ➡ 53%
We engaged in a preliminary discussion regarding V1 and V2 documentation with the highlights being:
bp.apiRequest to wp.apiRequest. (BP REST API Handbook)In other words, V1 should be cleaned up prior to the creation of the V2 documentation. Additionally, @im4th granted limited administrative access to developer.buddypress.org (this where the V1 documentation currently resides) for @vapvarun and @emaralive.
And, lastly, there was recognition that a tool or tools could help facilitate the creation of documentation from in-line (code) docs and from web based docs/handbooks. The former (in-line) is unclear and the scope needs to be further defined, however, there is a tool that does a portion of this for “actions” and “filters”, as well as WordPress tools, e.g., WP Parser. For the later (web based docs), there is a tool that will convert WordPress (web based) documents into .md (GitHub flavored) markdown files, e.g,, potentially be able to archive the V1 documentation, although those with the requisite permissions could export the V1 documentation, which then becomes a partial process which requires additional processing to convert the export into markdown files.
Our next documentation meeting will happen on September 4, 2024, at 19:00 UTC in #BuddyPress.
We set a date to release BuddyPress 14.1.0. September 4th, 2024. This is a minor release with two bug fixes and one enhancement.
We have a day and time scheduled for a group call about the new BuddyPress standalone theme for buddypress.org. The last piece missing before the call was an agenda. @vapvarun suggested a pretty detailed one, of what we need to get out of the call with:
It will happen on Wednesday September 11, 2024 at 18:00 UTC in #BuddyPress.
Our next development meeting will happen on August 28 at 18:00 UTC (an hour earlier than usual!) in #BuddyPress.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments’ area of this post.
Mark your calendars! We’re aiming to release BuddyPress 14.1.0 in early September. While there aren’t any urgent issues at the moment, we’ll be doing a final review in our next dev-chat to ensure everything is shipshape.
Our team is already hard at work for BuddyPress 15.0.0, and we’ve got some exciting features and improvements in the pipeline:
We’re also considering ways to improve the backend configuration process, making it easier for end-users to set up and manage their BuddyPress sites.
Our team has already closed 14 tickets for the 15.0.0 milestone, with 42 more currently open. We’re in the process of reviewing these tickets and prioritizing them for the upcoming release.
We’re tentatively planning to release the first beta for BuddyPress 15.0.0 in mid to late October, with the final release coming 1-2 weeks after WordPress 6.7 (expected around November 12, 2024).
Additionally, we’re exploring the possibility of a new standalone theme for buddypress.org. Stay tuned for updates on this exciting project!
It will happen on Wednesday August 28, 2024 at 18:00 UTC in #BuddyPress.
BP Documentation tracker status:
Documentation progress has risen to 47%, up from 44%. This reflects ongoing improvements in the quality of documentation.
Today, two new pull requests (PRs) were submitted:
The meeting also addressed numerous open tickets that remain unassigned. Previously, these tickets were default-assigned to @imath. The team will select 1-2 PRs for each meeting to manage these tickets more effectively.
Additional topics discussed included:
A new workflow process was agreed upon, where issues will be marked as “In progress” as soon as someone self-assigns them. This change aims to improve task management and ensure clarity on active work. The team will continue to focus on managing and reviewing PRs related to FAQs and bug reporting.
Our next documentation meeting will happen on August 21, 2024, at 19:00 UTC in #BuddyPress.
Hi!
Our next documentation meeting will happen on August 21, 2024, at 19:00 UTC in #BuddyPress.
Here’s our agenda:
If you have specific or additional points to discuss, please do so in the comments section of this post.
Hi!
This will be my first meeting as🧑🏾🍳 15.0.0 Release Leader. So be gentle with me! =P
Our next development meeting will happen on August 14 at 18:00 UTC (an hour earlier than usual!) in #BuddyPress. This is the new time for the dev chat during the 15.0.0 milestone.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments’ area of this post.