We merge feature into dev when we want to show a feature to a fellow developer.
We merge feature into staging when a feature is ready to be tested by non-developers and to be included in documentation.
We merge feature into production when it's ready for all users.
Has been working out well so far.
Wouldn't you just show them the feature branch?
In your example feature-B shouldn't have made it to dev.
For some projects though this is a bit overkill and if you don't think this is important chances are you can get away with something more akin to the branching model rorykoehein posted.
It seems really odd to me to branch from master for a feature branch, then push that to master, then push the feature branch to staging, and then push the feature branch to production. Is that what you are doing?
edit: spellign
At my workplace we have branches for dev, staging, and production. We're working on feature branches. Now if my coworker merges feature A into dev, and I merge feature B into dev, and feature A is done and ready for release, but feature B needs more work, and my coworker checks out a new feature branch C from dev, he'll be unable to merge into production without merging in my unfinished feature B.
We branch off of production so this won't happen. Are we doing it wrong?