odoo/upgrade#7280
Created by SM Engagement, Julien Banken (jbn)
Statuses:
- ci/runbot: Test upgrades between stable versions
- ci/upgrade_enterprise: Test upgrades for enterprise master
- label
- odoo-dev:master-event-bye-bye-jitsi-jbn
- head
- d25a6bfe2d918ad87ddc8c7324402f322b231fe9
- merged
- 8 months ago by Upgrade, Christophe Simonis (chs)
| odoo/odoo | odoo/upgrade | |
|---|---|---|
| master | #198587 | #7280 |
[REM] website_event{_exhibitor}/saas~18.3: remove jitsi related modules
Over the years, the Discuss module has evolved significantly, now offering seamless video conferencing capabilities. With that module, users can easily create video conference rooms and invite external participants with just a few clicks.
As a result, the Jitsi-based modules previously used for video conferencing in the event and website modules have become redundant. To simplify maintenance and eliminate duplicate functionality, we will be discontinuing these Jitsi integrations.
Moving forward, you can create video conference rooms by:
1. Opening the Discuss module
2. Clicking the "Start a meeting" button
3. Sharing the access link with your attendees
This PR removes the Jitsi-based modules and the fields they introduced in the client database.
Goodbye, dear Jitsi modules. You may be gone, but you will forever remain in our hearts. Press F to pay respects.
See odoo/odoo#198587
> Warning Please follow and check the relevant boxes for your PR, otherwise the review may take longer.
For a PR that adds a new upgrade script (for the Odoo's master branch or one of the RR versions):
- [x] I've added the references to the Enterprise and/or Community PRs in the commit message, even if they are already merged.
- [x] I've added an overall description of the changes made in the Community/Enterprise branches.
For a PR that fixes an issue on an already existing upgrade script:
- [ ] I've added a clear description of the issue including information on how to reproduce it.
- [ ] I've tested the fix and included references of upgrade requests where this fix will be applicable in the form of upg-<request_number>.
- [ ] I've included references to the OPW, if applicable, in the form of opw-<ticket_number>.
- [ ] I've tested this fix on other DBs, not just the ones with the issue.
For all PRs:
- [x] My commit's title follows the right format.
- [x] My commit's body includes information about the changes.
- [x] I've added odoo/upgrade as a reviewer.
- [x] I've read and understood this list.
- [x] I will ensure all the CI checks are green.
> Note More info can be found in the wiki.