To my knowledge, there aren't specific naming convention for branches. However, it's wise to use names that are easy identifiable, like tasknames or abbreviation for work. We are using JIRA for tasks and use the JIRA ID when naming the branch.

Regards,

Michel Kraaij - van den Berg

Valori ~ Innovation starts with testing

We are using JIRA  -Ticket ID and ALM / Rally - Story ID / Defect ID as the branch name. It helps to track the rules changed after the branch has been merged to the main rulesets by doing content search.

Rulesetname+_+Functionality/Bugfix/defectid+branch would be easily readable and can be differentiated.

We have made good experience with using the initials of a (lead) developer in the beginning and then either an abbreviation of the functionality or a defect number.

The initials help in identifying quickly whom to reach out to in case of questions related to this branch.