I suggest that, rather than voting, you work with your developers (or just senior developers if the team is too large) to get a consensus on how to amend the way you do version control. The reasons for this are (in no particular order):
- The rest of the team may have good suggestions that you haven't come up with.
- Voting tends to be a win-lose situation, and if you have more than one alternative likely more than half of the team isn't going to be in favor of the solution chosen.
- Voting isn't necessarily going to reflect serious thought on the part of the voter.
Remember that your developers are key stakeholders, just like your customers. In fact, if you look at changing the version control system as a project in and of itself, they are the customers. Engaging them in a discussion and achieving a consensus on why changing the version control system is beneficial, precisely what should be changed, how it should look at the end etc is IMHO better than presenting them with a short-list of alternatives.