StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGood Mercurial workflow for a team of 15 developers
primarykey
Id
3558243
data
AcceptedAnswerId
3558990
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-24T15:42:28.603
FavoriteCount
3
LastActivityDate
2013-09-02T09:29:01.840
LastEditDate
2013-09-02T09:29:01.840
LastEditorUserId
351696
OwnerUserId
351696
ParentId
0
PostTypeId
1
Score
5
ViewCount
1423
LastEditorDisplayName
text
Body
I'm in a team of 15 developers currently using Allfusion Harvest. We're not happy with it and looking around we've decided to switch to Mercurial due to the available frontends TortoiseHg and MercurialEclipse. We're currently using a twelve year old release of Harvest and I find our current workflow hard to translate to Mercurial. I have previous experience with ClearCase where we used a model similar to: <pre><code>A A A | | | B C | | /| | C | E | | / D E | / E </code></pre> Where the left trunk is unstable, middle is test and right is stable. Now I have no problem recreating this branching model in Mercurial (in one central repository). The idea is that the developers then clone this repository, branch out from unstable, do their work and then merge with unstable. Reading on the web I've yet to see a Mercurial work flow aimed at teams larger than three developers so I'm unsure if this is a good workflow. So two questions: Is this a good working model? How do you work with Mercurial and how many are there in your team? EDIT: Since asking this question I've used both <a href="http://nvie.com/posts/a-successful-git-branching-model/" rel="nofollow noreferrer">Gitflow</a> and <a href="http://scottchacon.com/2011/08/31/github-flow.html" rel="nofollow noreferrer">Github flow</a>. Both has been useful depending on release complexity and team size. And when using Mercurial I've stopped using branches (for other than stable/unstable) and made use of the Git influenced bookmarks instead.
Tags
<mercurial><workflow>
Title
Good Mercurial workflow for a team of 15 developers
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMdaG
UserOwnerUserId
1. USMdaG
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGood Mercurial workflow for a team of 15 developers
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGood Mercurial workflow for a team of 15 developers
 UserUserId
 USTammo B.
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POGood Mercurial workflow for a team of 15 developers
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.