Allow the version control system to be pluggable
Allow the version control system to be pluggable. Allow someone to use the built-in VCS, SVN, Git, Mercurial, etc with TFS.
I know many people who LOVE what TFS can do but HATE the source control. I have no problem with the source control but I think you’d see adoption skyrocket!
4 comments
-
Derek Licciardi
commented
This would be a nightmare for transparency. Most of the products asking to be integrated have no love for anything Microsoft. Open Source Sortware comes to mind. Transparency would suffer. Traceability would suffer. How is work shelved and unshelved as tasks move from in progress to todo and back? What analogies need to be mapped between source control systems for shelvesets and changesets? These are fundamental concepts to the entire TFS system working properly. I can't see how CVS, Git, Mercurial, etc., etc. would map consistently unless each product released a TFS version.
-
Andrii commented
And make fast switch of TFS servers and Source Control systems.
Something like Team Explorer but with combobox or treeview of Source Controls servers I plugged in.
So I can just click on it and connect right away. -
Neno
commented
Can you elaborate what benefits this would give the users?
-
Bryan commented
I wouldn't pick a DVCS specifically - but allow it to be pluggable - I personally am very comfortable with the TFS VCS, but Git and Hg have large followings and adopting TFS for all of the other goodness would be great without having to change over the Source Control System for an organization