Invitation for Thoughts on 'How do you branch for code promotions and handle your build definitions and common build scripts'
The title says it all. I have been playing around with a number of scenarios of how to best handle code promotion branches, or any other branch for that matter in which you need to ensure that your build script versions stay in tact with that branch. The build scripts I use tomorrow will not build my code of today. With how Team Build 2008 better leverages using a starting build script located anywhere in the tree there are much better branching options that help keep your builds synced with what it is they should be building. But there is much to consider- such as those common build scripts.
So... the question is what sorts of code promotion patterns are people using with TFS to come out the other side with the needed builds for the new branch with the proper versions of build scripts.