Although we do not support granular permissions on branches, a previously suggested approach would be to fork the repository, providing the Release Manager access to the fork.
The fork can inherit or have its own permissions. As part of the release, you could ask the manager to pull incoming changes from the parent.
This information can be found here if interested:
I hope this response was helpful.
Jason | Atlassian
The lack of "push" write access control per branch, or at least to a single ("master") branch, is causing is a lot of trouble. What are the odds of this appearing? We're trying to decide whether to endure for a while (and manually push -f back a bad commit in master every few days), or look elsewhere.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events