the user story that i desire is a label that someone with the commit bit can move around freely, and then it gets automatically synchronized to everyone else who pulls/fetches the repo (i.e. *without* reading multiple blog posts and issuing multiple git commands).

a release branch, especially with force-pushed commits, is rather far from that in terms of the user experience. but then maybe i should learn to love merge commits...

now, how exactly git behaves is another story. it never seizes to surprise me.

(i'm fine with calling the "stable" label as "release", or whatever else. the actual name wasn't my point.)

- attila