• See previously BP Dev Chat summary July 10 (2024)
• In attendance: @vapvarun @im4th @emaralive @dcavins @espellcaste
• Slack archive

🧑🏾‍🍳 15.0.0 Release Leader

@espellcaste renewed his interest to lead the 15.0.0 release. As he has a fixed professional meeting call at 19:00 UTC, @im4th asked other members of the team if everyone was ok to change our meeting time to an hour earlier at 18:00 UTC. Some of us might not be able to join at some meetings, but the majority thinks we’re good to go with this earlier time during the 15.0.0 development cycle.

We’re happy to announce Renato Alves (@espellcaste on WordPress.org, @renato on Slack) is the leader of our next major release (15.0.0) 💪 🇧🇷 😍 🎊.

🧟 Deprecated code in 14.0.0 & up

We took the time to review the way we load deprecated code. Since 11.0.0, we usually:

• Load last 2 versions deprecated code when BuddyPress is upgraded.
• Skip this deprecated code loading for BuddyPress fresh installs.

As 12.0.0 was a huge revolution, we carried on including 12.0.0 deprecated code in 14.0.0 fresh installs and upgraded ones to take in account the fact, unfortunately a lot of Plugin/Theme developers haven’t updated their code to be fully ready for 12.0.0 yet (See #9210).

After discussing about it, we decided:

• When BuddyPress first installed version is up to 15.0.0: we carry on loading 12.0 deprecated code.
• We’ll add a notice in 15.0.0 to inform it’s the last version of BuddyPress to load 12.0 deprecated code.
• We’ll post a developer note on this blog
• We’ll add an item into our plugin’s FAQ, as well as post a resolved support topic about it.
• We’ll add a deprecation policy into our documentation (#bp-documentation-290).

NB: to force the deprecated code to be loaded, users can always define( 'BP_LOAD_DEPRECATED', true ); into their WordPress configuration file.

🍇 Merge the v2 of the BP REST API into BuddyPress trunk

We had a quite long discussion about this point to find the best way to deal with deprecating the v1 of the BP REST API. As we’re a small team, maintaining 2 versions of the BP REST API is not doable. Here’s what we finally decided:

• The BP REST API code will be merged into BuddyPress trunk and updated to v2 🙌.
• The BP REST plugin will be archived and a release of it will be packaged to let users eventually override v2 with the deprecated v1 in case they need it 🧟.
• buddypress/v1 routes will offer a different message than “No route was found matching the URL and request method.” to inform it’s deprecated when the BP REST plugin is not active.

📆 Next Dev-Chat Agenda

It will happen on Wednesday August 14, 2024 at 18:00 UTC in #BuddyPress.

#15-0-0, #dev-chat, #summary

• See previously BP Dev Chat summary July 3 (2024)
• In attendance: @vapvarun @im4th @emaralive @dcavins
• Slack archive

✅ BuddyPress 14.0.0

This meeting main goal was to check we made enough progress to package BuddyPress 14.0.0 on July 12. Short answer is yes as it was released on this day!

• Credits list: @vapvarun worked on it and shared it with us at the very beginning of our chat.
• Announcement post: @im4th volunteered to write it out of the BP Hello Screen and asked @dcavins to review it once a draft is ready. He agreed 😍.
• Full change log: this was the last task to achieve. @vapvarun volunteered and started right away to generate it for the Codex as a bit before the end or our meeting he confirmed it was ready.

We were confident about releasing on July 12, and we were right!

14.0.0 final schedule

• June 13: 14.0.0-beta1 ✅.
• June 24: 14.0.0-beta2 ✅
• July 5: 14.0.0-RC1 ✅
• July 12: 14.0.0 ✅.

🔮 BuddyPress 15.0.0

• @im4th started to share about the little complexity introduced by our new way of branching (right after the release candidate version): we need to be careful to commit a fix twice or 3 times during the period between RC and final release:
  • trunk,
  • new branch,
  • & possibly old branch in case the commit is a regression from the previous plugin version.
• Who’s volunteering to lead 15.0.0 release?
  • @dcavins won’t have enough time to commit to leading
  • @emaralive thinks it should be someone that is not him 😄.
  • @vapvarun will monitor all 15.0.0 steps to be ready to lead 16.0.0.
  • @espellcaste wasn’t around during the chat, @im4th said he thinks he was interested to lead 15.0.0
  • Let’s decide about it during our next development meeting.
• There are already more than 70 tickets into the 15.0.0 milestone 😅. @emaralive thinks we should straighten out registration/invitations/opt-outs + email notifications (it’s on @dcavins todo list!). @dcavins noted there were private messages improvements as well as caching/performance ones.
• @im4th thinks it would be nice to release 15.0.0 before the end of the year.

20 minutes about the very needed BuddyPress.org new theme

#9193 is the place where we can share/organize our ideas. @im4th shared with other members of the team the nice discussion he and @vapvarun had at Da Lucia’s pizzeria. What about using the Twenty Twenty-Four default WordPress theme and enjoy all possible customizations the Site Editor is providing? It’s an interesting idea to have this change: it would give us some time to work on a great new BuddyPress standalone theme as well as renew BuddyPress.org site’s appearance which has been the same for years! Finally @im4th suggested we really talk about it during a video/audio chat: let’s organize it soon 🎥 🎙️.

Next Dev-Chat Agenda

It will happen on Wednesday July 31, 2024 at 19:00 UTC in #BuddyPress.

PS: no chat next week! Next docs chat will happen on Wednesday July 24, 2024 at 19:00 UTC.

#14-0-0, #dev-chat, #summary