BuddyPress 6.1.0 is available for download from the WordPress.org plugins directory. It’s a maintenance release to fix 6 issues, please upgrade asap!
More info about it > https://buddypress.org/2020/06/buddypress-6-1-0/
@im4th will package this maintenance release next Monday (July 29).
The call for tickets is now closed. Many thanks to all the contributors who replied to it 😍
We agreed with @mercime about how it’s best to work on this:
To make it easier to new contributors to quickly get a testing environment to work on patches we’re discussing about including @wordpress/env to our building tools: #8317. Don’t hesitate to share your thoughts about it. During our meeting we’ve been talking about Docker’s compatibility with MS Windows powered computers.
We are also thinking at raising our WordPress required version to 4.9: #8318
Finally @im4th shared about the work he’s been doing about introducing a Block Based Activity post form. A detailed PR is available on the BP Blocks GitHub repository and you can also read this WP Tavern great post about it.
For this meeting we chose to focus on defining the next features the team will work on for the 7.0.0 development cycle as well as first information about the 7.0.0 release schedule.
At the end of our meeting we agreed on this schedule:
I’ve just updated the 7.0.0 milestone: let’s start contributing to this great release!
If you’d like to share with us your features wish-list, you’re very welcome to do so replying to our call for tickets.
BuddyPress 6.0.0 was released on May 14, we did the 6.0.0 development cycle review during our latest “dev-chat”, today we’re inviting you to contribute to 7.0.0’s kick-off by replying to this call for tickets (just like WordPress does before each release).
The priorities of the BuddyPress community matter, please let us know what:
To do so, you simply need to pick the ticket link(s) you think we should prioritize on from our code source management tool and paste them into this post’s comment form. If you’d like to, you can also share your ideas about the corresponding ticket(s). If some “already shared” tickets are also interesting you: use the ⭐️ Like feature to second them.
Here are some custom queries you can have a look on to get some! 🤔
PS: don’t hesitate to add a new ticket, if you haven’t found a match into the above queries 😉
PS2: Adding your ticket here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!
This call for tickets will end on June 17, but we’ll begin discussing about what we’d like to see in BuddyPress 7.0.0 during our next dev-chat (June 3rd) : so the sooner you share your wish-list the better!
Thanks in advance for your help and let’s all wish a great 17th anniversary to WordPress 😍🎂
6.0.0 was released on May 14. The first subject we’ve discussed about was checking for issues related to this release that may have been published into our support forums. @vapvarun has been very active on support forums lately and confirmed there wasn’t any topics specific to this release.
@im4th talked about statistics and more precisely about this release’s download pike. It was reached on May 15 with 28300 downloads: almost 5K more than the 5.0.0’s download pike.
@im4th congratulated all BuddyPress contributors who got involved into the 6.0.0 release and did a great work.
For @mercime we had more contributors, “Fast-and-furious commits” and we kept enough time for polyglots (2 weeks of string freeze) to let them contribute to the translation of the 6.0.0 release.
@dcavins was pleased by the activity & engagement of this release lead 😍.
@im4th was happy we could work on the priority we defined after the 5.0.0 release : work on getting more beta-testers to help us add the final touches to 6.0.0 : the BP Beta Tester plugin has been published on the WordPress.org Plugins directory and it does the job pretty well according to @dcavins “BP Beta Tester is fantastic“.
We also said we were happy:
PS: if you’d like to share your opinions about these two sections, you’re welcome to do so commenting this summary.
@mercime gave us the very first learnings of this survey:
Of course these points are temporary results. We’ll be more specific as soon as the survey will be ended.
As we were running out of time @im4th suggested to publish a call for tickets on this blog, just like WordPress does on their Make WP/Core blog. We also agreed to think about it for the next 2 weeks and use our next development meeting to share our ideas. @IAmTheWebb suggested to organize a survey to “ask for feedback on features people would want“. @im4th thinks results of such survey are a bit difficult to use. We’ve experienced it for Blocks and we were not so convinced by the involvement it got. He also added he’s rather have something like “what feature do you want to contribute to for 7.0.0 release?“. We’ll test the call for tickets, it’s a good way to show how we are contributing to BuddyPress on our tool to manage the BuddyPress code source.
Start picking the BuddyPress tickets, you’d like us to work on, we’ll soon publish the “BuddyPress 7.0.0 call for tickets” 😉
If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.
BuddyPress 6.0.0 is ready for download! > https://buddypress.org/2020/05/buddypress-6-0-0/
Many thanks to our 42 contributors, let’s upgrade to enjoy their great work 💪
We’ve been discussing about an a11y issue @mercime raised into this comment. @im4th said he will look into it asap to try to fix it before 6.0.0 release. The improvements @dcavins (many thanks for your help) brought to the initial patch has been taken in account during the first commit about the Hello Screen. We will add the link to the 2020 survey at the last minute. @mercime already opened a ticket on Meta Trac to request for survey banners on our sites (BuddyPress.org, the Codex and the Developer Ressources site). @mercime (many thanks to you too!!) also committed to update the props of the Credits Screen for 6.0.0. The 2 last steps about props are to:
Finally, we’ve listed the ultimate tasks to achieve before 6.0.0 release.
After @im4th‘s first pass about it less than 10 endpoints needed a review/update. He thinks it’s doable before the release date and since the dev-chat, it’s important to mention that @mercime has been doing an amazing job about it reviewing and updating 11 endpoints so far 👏🏆.
@im4th is confident we will be able to release it for May 14th. No blockers were raised during the meeting, so let’s do it !
It will happen on May 20 at 19:00 UTC (a week after release) 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!