mercurial - Bookmark-based hg workflow for open-source project -
in scons project, use mercurial bitbucket . we'd have several ongoing features under development different people (perhaps multiple people working on single feature, or single person working on multiple features). we've tried named branches, don't work feature development in mercurial. we'd git branch system, branches lighter weight , not permanent, still shared. other separate repos per feature, don't think we're ready (too radical), community seems bookmarks way go here; development on default branch, bookmarks each head (feature). first question: reasonable workflow? other projects working way? second question: having tried little, 1 thing that's confusing when hg update default it's semi-random head get; depends on 1 updated last. have hg update featurex or hg update featurey or else (a) land on random head, , (b) no bookmarks "activated" end not moving bookmark forward. seems recipe failure. assume i'm missing somethi...