A release must introduce a database field used by a new app version while old instances still run during rollout. Which database change sequence best preserves compatibility?

1. Add a backward-compatible schema change, roll out compatible code, then remove obsolete schema later
2. Rename the database without changing the clients
3. Delete the old field before deploying any new code
4. Require every rollout to ignore database compatibility