Once I get back into the coding saddle, I think I may start utilizing
branches for some of the more involved stuff, especially to get better feedback before making a commit to the trunk.
Anyways, I wanted to see if there are any policies or best practices that we would want to follow, as far as naming convensions for branches, limits to how many we should create, etc. Specifically, should we just create 1 for our own changes we're working on, or would be be better to create one for each special (major?) feature we're working on (eg, spells loaded via db, AA skills calculated in the mob class, combat changes, etc).
Any thoughts?