As teams scale to multiple releases daily, the traditional practice of tagging commits becomes obsolete. The focus shifts to trunk-based development, where the trunk is never frozen, allowing for rapid releases while maintaining a policy that restricts additional features post-branch cut. Bug fixes can still be cherry-picked to the release branch, ensuring that only essential changes are included before going live.
