Bookmarks usage survey

[Jensen, Aaron]

> 1) Do you use bookmarks? How do you use them/what does your workflow look like?

We're about to roll them out in a limited function to track our weekly releases, one bookmark on our build server for each weekly release. Changes sit in our test environment for a week before going live. We use the bookmarks so developers can make fixes in the appropriate places: the pending release, the live release, etc.  We use them so that it the bookmark follows developer commits when they pull down a release to their computer, make changes/bug fixes, then push back.


> 2) Are they working well for you? Any pain points?

We haven't rolled them out yet, so nothing to say yet.  Ask again in September. :-)


> 3) If you don't use them, is there something preventing you? What do you use for feature branches instead?

I investigated bookmarks for widespread developer use.  I really like the feature, especially for short-lived feature branches, which we have a lot of.  Unfortunately, there was one behavior that prevents us from using them: `hg up` will move a bookmark [1]. This makes it WAY too easy for a developer to do the wrong thing and not even realize it. I expected bookmarks to be more "branchy" and only move if: 1) I commit a change or 2) I explicitly want it to.

[1] http://selenic.com/pipermail/mercurial/2013-October/thread.html#46095