Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
Today we are releasing the final TFS Beta 2 test patch. This patch is for the client and has a few nice bug fixes in it. Again, if you get the chance to try it out, please let me know if you have any issues.
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=25422
or
http://code.msdn.microsoft.com/KB978148
Note, the code.msdn.microsoft.com link is still in the process of publishing so you may still get an error for the next few hours.
Here’s the list of bug fixes:
Brian
It seems TFS has a very Poor Promotion tracking model:
(See this thread)
http://social.msdn.microsoft.com/Forums/en-US/tfsprerelease/thread/0203c247-3113-4563-a60b-61aa3fc54490
Here is one of the many chains we went down to try to resolve:
http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/039c5945-dee2-4b2b-908f-4970955ca809
We would greatly appreciate some improvement in TFS2010
Thanks for the detailed response here. I've looked over the forums thread that you referenced as well, and I have a few comments:
- I agree that having the labels inline in the history would help in this and other scenarios. This is on our backlog, and we hope to include it in the next release.
- We also hope to include a feature to lock labels to be sure that they don't change after they are labeled. This is also on our backlog.
- The main goal of the Tracking Changesets feature in 2010 is designed to help solve the problem of understanding if a change was merged into another branch (which is close to what you're asking for). I understand that if you're looking for a list of changes in a branch, this could be a tedious process. We're also talking about how we might provide a feature to present an aggregate view of changes that aren't included on a particular branch. That idea is really just in the earliest stages, but I expect us to provide at least a power tool at some point in the future.
- One of the points that Ed Blankenship made on the forums was that there are ways to work out solutions for TFS to solve the problems your team is having challenges with today. Maybe the standard branching model isn't the right solution, but there is surely a way that would meet your needs. I think his suggestion of seeking some of the expert partners that we have could be of help.