I completely agree with you on this. Bubble needs to run a stable production framework that doesn’t receive any changes unless the community is given prior notice and preparation.
If they release an update to a dev/staging cluster then users would have an opportunity to report the bug and Bubble could fix it. Rapid iteration is very good and can be very bad if not done well. I think this policy should be given further consideration.
Two seemingly good options:
- Lock production/live apps from receiving any changes without said notice
- Allow apps to run on the current version OR the previous version of the Bubble platform. Then if they push a change that breaks, individual apps could choose to rollback to the previous version of the platform, report the bug to Bubble and switch back to the current version when the bug was patched/resolved.