We're integrating Mercurial slowly in our office and doing web-development we started using named branches.  We haven't quite found a good convention as far as naming our branches though.  We tried: FeatureName (Can see this causing problem down the line)DEVInitial_FeatureName (Could get confusing when developer come and go down the line){uniqueID (int)}_FeatureSo far the uniqueID_featureName is winning, we are thinking of maintaining it in a small DB just for reference.It would have:branchID(int), featureName(varchar), featureDescription(varchar), date, who etc...This would give us branches like: 1_NewWhizBangFeature, 2_NowWithMoreFoo, ... and we would have an easy reference as to what that branch does without having to check the log.Any better solution out there?
Good naming convention for named branches in {DVCS} of your choice
version control;mercurial
If you don't have an issue tracker, I recommend setting one up and then using {issue tracker name}_{ticket number}. When someone years from now files a bug and you don't know exactly how the feature was supposed to work, it'll be easy to annotate the file and get back to where the user may have requested that exact functionality.