Groups
Groups
Sign in
Groups
Groups
BigBlueButton-dev
Conversations
About
Send feedback
Help
BigBlueButton 3.0.11 released!
83 views
Skip to first unread message
Ramón Souza
unread,
Jul 17, 2025, 4:35:36 PM
Jul 17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BigBlueButton-dev
We are pleased to announce BigBlueButton 3.0.11!
This 3.0 iteration contains various client and server side fixes.
Linked is a list of the pull requests in this iteration, grouped by component.
Link to installation command / instructions / features :
https://docs.bigbluebutton.org/3.0/new-features
The full release notes are here
https://github.com/bigbluebutton/bigbluebutton/releases/tag/v3.0.11
To try out 3.0.10, visit
https://demo.bigbluebutton.org/
If you want to report any potential security issues with BigBlueButton, please check
https://github.com/bigbluebutton/bigbluebutton/security/policy#reporting-a-vulnerability
As always, we welcome feedback on this latest update.
Ramón and team
Ramón Souza
unread,
Jul 21, 2025, 10:42:50 AM
Jul 21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BigBlueButton-dev
Hi everyone,
We received a report from the community of a regression in BigBlueButton 3.0.11, see
https://github.com/bigbluebutton/bigbluebutton/issues/23576
.
We've confirmed the issue and are working on a fix that will be available shortly in 3.0.12,
https://github.com/bigbluebutton/bigbluebutton/pull/23580
We recommend holding off on updating or deploying 3.0.11 release until 3.0.12 becomes available (soon!).
Thanks again for the folks that reported this so quickly. We'll share another update as soon as the fix is released.
Reply all
Reply to author
Forward
0 new messages