How to build a frontend release?

Question

Project management

Hello! Tell me how to collect the release?
There is a frontend development team.
The team is cutting features, each in their own branch. After the readiness, according to the developer, the feature is uploaded to the test environment (it is 1).
The team wrote down 50 features and submitted them for testing.
During the testing process, bugs are corrected in the test by different developers (it is not always clear whose task gave rise to the bug).

Then X day comes.
In the test environment, all 50 features are tested, bugs are fixed. And the manager says - "we will upload only 40 of them for the battle, the rest in the next release."

How to extract these 40 features from the tested version without pain? Who organizes the process and how best?

Answer 1

Each feature, by default, should have its own branch and merge the working and necessary for the release into the main one during work.

Answer 2

So plan your release.

Answer 3

The (front-)architecture of the project must support such a manager.
Have the possibility of "painless" feature shutdowns.

Answer 4

And how did you plan your sprints, if there can be such a scatter between what you have done and what you will be rolling out to the release ???