changes for 2.2.34

[cjhille]

AFAICT some changes might need to be added to the repo to support the jump from 2.2.31 to 2.2.34

• akka-bbb-apps/src/universal/conf/application.conf
• record-and-playback/core/scripts/bigbluebutton.yml
• bigbluebutton-html5/private/config/settings.yml

@alangecker I would have created a PR, but I'm not sure how your process for upstream diffing works and if I've missed something. Could you elaborate on the process or maybe provide an update for 2.2.x? 😇 I'm asking because in my built of 2.2.31 the kurrento container keeps crashing every 24 hours and I'd like to update the entire BBB setup to a more current and hopefully stable version.

[alangecker]

hey @cjhille
cool that you think about creating an update to 2.2.34! :)
haven't got time for that recently...

This always consists out of following steps

1. Get an understanding about every change that happened and find out what changes to bbb-docker that require.
   Note, that quite often there are changes made which are not accessible in the bigbluebutton/bigbluebutton repo, so you should rather look through all the related commits in alangecker/bbb-packages
2. Apply these changes to this project.
   • Quite often you only need to set TAG to the corresponding release tag in bigbluebutton/bigbluebutton like v2.2.31. To avoid the unnecessary recreation of images, only change the TAG of those components, which actually received a change.
   • New config variables are also quite common
   • don't forget to checkout a newer version of bbb-webrtc-sfu if it also happened in the release. you can find out what the current version is here
   • sometimes it requires bigger changes like with the introduction of the dockerized libreoffice or the upcoming split of meteor processes, but this should not happen anymore to v2.2.x
   • if available, you can also think about switching to more recent images of kurento, etherpad, nginx, etc.
3. Test everything (with firefox and chromium/chrome)
   • Audio
   • Video
   • Presentation upload
   • Shared Notes
4. Create a CHANGELOG.md entry
5. Create a Pull Request
6. Receive big thanks from @alangecker

[cjhille]

@alangecker, thanks for your comprehensive write-up. Here I though I could get away with just updating the few .conf and .yml files ^^, but clearly there is way more work involved in the update process.. that is, if you start from the valley of miniscule knowledge where I come from.

Especially the part of understanding the code changes through (slightly) obscured + sqashed debian package diffs (in absence of commit messages) and using API-mate to test the reintegration efforts seems daunting on a very limited time budget and is also quite frankly a little over my head at this point. I am sorry to disappoint you and myself :(

On the other hand, your step summary has given me a good idea how the process works and I would suggest to add it as an entrypoint to a contribution guide on the development "How To".

Lastly, seeing the effort it took (and is still taking) to get this big blue behemoth dockerized makes me all the more grateful for your initiative and hard work. Thank you.