- See previously BP Dev Chat summary (September 18)
- In attendance: @boonebgorges @dcavins @offereins @espellcaste @im4th
- Slack archive
5.0.0 development cycle report
BuddyPress 5.0.0 was released on September 30, 2 days before this dev-chat happened.
@boonebgorges was the first to share his feedback about this release. He congratulated the “5.0 team” for their amazing contributions.
@im4th sent new props to all 5.0 contributors and informed about the first results of the release in terms of downloads. The spike was reached on October 1st with 23562 downloads (~1K less than the one we had for 4.4.0). At the time of the dev-chat, no support topics were posted about issues relative to the 5.0.0 upgrade.
We unfortunately had an issue with po/mo language packs generation. Thankfully, the Meta Team fixed it very quickly and we updated our release process to make sure it won’t happen again.
What have we done well?
For @espellcaste we kept our development meetings (dev-chat) consistent (every two weeks). He also think publishing development notes during the development cycle and before the release was a good practice.
@im4th thinks having the BP REST API documentation ready before the release was a great team achievement. Developing the BP REST API from GitHub was also a great way to save some time (especially when rebasing!)
What can we improve?
We all noticed testing involvement was very low during 5.0.0 beta tests. We’ve tried to understand the reasons behind this fact:
- lack of interest?
- lack of time?
- lack of visibility of our communication?
- total confidence in our work?
It’s important we try to reach and get the involvement of early adopters, advanced users, plugin and theme developers during BuddyPress major release beta tests.
@im4th then asked if the frequency and the schedule time of meetings were suitable for all. The “every other Wednesday” seems to be fine with everyone but moving the schedule time to one hour earlier seems better.
What’s next in BuddyPress?
The first priority is to complete the BP REST API with the remaining endpoints (#7156).
About the Gutenberg project and to follow up with a previous conversation we had about it. We need to have a better idea about BuddyPress users needs on the BuddyPress Blocks (#8048) topic: that’s why we’ll share a poll with them. @dcavins thinks the obvious first step is to have a block version of our existing widgets: we all agreed. About the poll, as @boonebgorges pointed out we might have a very limited participation to it, so we will have to analyze the results very carefully. He also pointed out the poll was to consider as one input like any other. @im4th will work on a text about it in order to be able to explain and share the poll on this blog and on one BuddyPress forums topic.
@im4th thinks that more than blocks BuddyPress users are expecting a “BuddyPress maintained” component to manage User Media (#8022). He plans to revamp the BP Attachments plugin he started a while ago to try to have something ready for 6.0.0.
@im4th is also planning to work on migrating the way BuddyPress builds URL to use the WP Rewrites API (#4954). He thinks that as it’s a breaking change, we need to build it so that it can be “tested & deactivated” for a while.
How can we have more betatesters?
@im4th shared his ideas about this potential improvement we all agreed on during our 5.0.0 cycle development report:
- A beta tester plugin just like the WordPress one, but for BuddyPress.
- Migrate this blog into the BuddyPress.org network (#5525) and extend it to include a handbook about contributing to BuddyPress.
How can we improve the way users get help?
Unfortunately we ran short of time and decided to talk about this point during our next dev-chat.
PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!