- See previously BP Dev Chat summary (October 7, 2020)
- In attendance: @vapvarun @IAmTheWebb @dcavins @im4th
- Slack archive
7.0.0-beta1 feedbacks
7.0.0-beta1 was released on October 16. So far, nothing specific to it was posted into our support forums. At the time we had the meeting, @im4th, thanks to @IAmTheWebb tests, had reported an issue (now fixed) with the Activity Embed block into our Trac environment. This last Friday @k3690 reported a wrong usage of the member term into a Group Type meta property (now fixed).
7.0.0 remaining tickets
- #8292 @vapvarun submitted a patch during the meeting 💪, @im4th reviewed it some time after, brought some minor improvements and it has been fixed yesterday. It’s now possible to assigned more than one member types to users from their WP Admin Extended Profile 🙌 .
- About #8179, @im4th asked @vapvarun to update the ticket with 2 squared corner avatars with these dimensions: 150px x 150px (full) & 50px x 50px (thumb). @im4th will try to progress on a patch in the meantime.
- We’ve postponed #8093 (Profile Field visibility improvements) to a next milestone.
- #8375 was reopened by the reporter, as the filter we’ve added wasn’t matching its needs. @dcavins @johnjamesjacoby & @im4th have been discussing about it last week in #BuddyPress and came to the conclusion a possible better place to allow the invitation table’s name filtering was to include the
{$bp_prefix}bp_invitationstable name into theglobal_tablesproperty of theBP_Members_Componentobject. @dcavins will investigate this week about that possible change. - Finally shortly after our meeting, @boonebgorges reported a new ticket about improving the
xprofile_get_field()function so that it only pulls up the data for a field when necessary. The patch he suggested as a first step looks safe to @im4th who thinks it should be included into the 7.0.0 release: it’s always great to improve DB performance. Please have a look at #8378 and send him some feedbacks about your thoughts.
7.0.0 release schedule update
We are going to package a new 7.0.0-beta to include as much fixes as possible considering the previous chapter. Packaging will happen shortly after our next BP Dev-Chat.
- 7.0.0-beta2: November 4th
- 7.0.0-RC1: around November 18 (string freeze).
- 7.0.0: December 1st 🎯
7.0.0 release tasks
The following list of tasks needs to be achieved before we package our next major release (7.0.0).
| Tasks | Owner |
| BP REST API documentation updates | @im4th |
| BP Survey results | @im4th |
| 7.0.0 Release note | @vapvarun |
| 7.0.0 Credits update: – BuddyPress Trac – BP REST GitHub repository | @dcavins @im4th |
| 7.0.0 Pizza Restaurant name | @dcavins |
| 7.0.0 Announcement post | @im4th |
NB: we’ll also need to add a patch to #8376 to update our “Hello BuddyPress” modal.
GitHub default branch naming for BuddyPress repositories
This point was moved to a future development meeting. @johnjamesjacoby shared his thoughts about it. Possibilities are main or trunk. FYI WordPress contributors decided to use trunk for repositories of the WordPress organization on August 19.
Open floor
@dcavins asked a question about using the new BuddyPress development environment: when making changes to the BuddyPress source code, he was wondering how is updated the running environment? In other words, do we need to run some specific commands to update it?
@im4th replied changes were automatically taken in account without doing anything more than saving the BuddyPress source code changes. @IAmTheWebb confirmed: “the folder you see outside docker is mapped to inside, so changes you make should appear automagically“
Next Dev-Chat
It will happen on November 4 at 19:00 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!
