Be ready to roll back; sooner or later you will need to do it. Remember, You don't need more QAs you need a faster rollback. If anything goes wrong in production, the first thing you want to do is to play safe and come back to the last working version:
- Develop a rollback strategy and the process of what to do when the system is down
- Split non-backwards-compatible database changes into compatible ones
- Always use the same process of delivery for rollbacks and for standard releases
- Consider introducing blue-green deployments or canary releases
- Don't be afraid of bugs; the user won't leave you if you react quickly!