We used to have the usual regular software releases - once or twice a year - and branched our code in TFS in order to support hotfixes or patches - whatever you want to call them.
Now we are releasing a new version every two weeks and are trying to figure the best way to manage hotfxes. One option of course is just to assume people will upgrade to the latest version, but in some cases that isn't practical, so I was trying to think of how TFS could support this.
Each release gets labelled, so getting the original code isn't a problem, it is making sure you have the current patched code if no branching is being done.
I did wonder about having each developer check in their hotfix changes to a shelveset with the label name in it - so getting the latest hotfixed version would be a matter of finding all the shelvesets containing that label name and checking them out in date order, but TFS doesn't support searching on shelveset names.
I then wondered about developers sharing the same shelveset - to the same shelveset would be used to store all the hotfix changes for a particular version - but developers can't check in to a shelveset that someone else created.
So can anyone think of a good solution to this?