I think to some extent this is a personal preference, but there are definitely strategic ways of thinking about it.
I try to release new feature sets in batches that make sense with the planned work on a project. If I know there are two new features I’m working on at the same time, I’ll release them together. Separately, if there are bug reports, I’ll try to release fixes to those as soon as I can, depending on how critical or urgent the bugs are.
If they can wait until I’m done with my two new features, I’ll do it all at the same time. But if users were getting access to data they shouldn’t, I’d fix that immediately. The key with a fix like this one is that if you’re working on other features or sections of the project at the same time, then you should try to hide those changes when you push the bug fix live (maybe you just make all the key elements invisible or disable certain workflows), so the new partially-complete features aren’t actually live to users yet.
A feature that Bubble recently released that helps greatly with this is having multiple versions (or branches, or workspaces): [New Feature] Multiple versions. With this, you can jump into a new version to fix a bug, while keeping your other, unfinished work separate.
In general, you should use your intuition to see what makes sense when balancing timelines and criticality in your project.
—
Kevin
AirDev
We’re looking for Bubble developers to join our team: https://jobs.airdev.co/