What process is commonly used to stabilize features before a release?

The practice of creating release branches is a common strategy used in software development to stabilize features before a release. This involves creating a separate branch in the version control system that is dedicated to the upcoming release. By doing so, developers can isolate the release version of the software from ongoing development work, allowing necessary bug fixes and final adjustments to be made without interference from new feature development that is happening in the main branch.

This approach helps ensure that the code intended for release is stable and thoroughly tested. It allows teams to focus on fixing bugs and optimizing performance, as they can prepare the release version without worrying about changes that may be introduced by other developers working on new features. Stabilizing in this manner ensures that the release is of high quality, meeting user and business expectations.

In contrast, options such as integrating changes from the Master branch or developing new features concurrently could lead to instability, as these actions could introduce new bugs or issues into the release candidate. Similarly, while removing untested features could be part of a stabilization strategy, relying on it alone is not as structured or systematic as creating dedicated branches for releases.