#YOUTUBE MICROSOFT TEAM FOUNDATION SERVER CODE#
Even the Linux kernel only had 9.2 million lines of code (circa 2007-2008) and most projects don’t come close to that figure. However most development teams don’t work like that.
#YOUTUBE MICROSOFT TEAM FOUNDATION SERVER DOWNLOAD#
If you support multiple versions of an application, and those versions are occasionally updated via service packs then they recommend what they call the “standard plan”. They call this their “basic plan” and it makes sense for continuous deployment scenarios where you don’t need to work on more than one version at a time. The simplest is to just have a branch literally called “RELEASE”. The theory is that if you only increment the version number in the main branch you can tell at a glance how long it has been since the development branch was last re-synced with its parent.įor the release branches, Microsoft offers several options. One specific recommendation remains from previous versions of the guide, Microsoft continues to advocate not incrementing version numbers in development branches. The initial guidance for the development branches are fairly light, as it often comes down to how your company organizes its teams and features.
There are two principal sets of branches coming off of MAIN, known as DEVELOPMENT and RELEASE. Known as the “trunk” to many, Microsoft refers to it as MAIN. Like most branching and merging guides, there is a main branch that serves as parent to all of the other branches. While ostensibly meant for TFS users, much of the advice is applicable no matter which source control provider you choose. Microsoft has released a draft of their new Branching and Merging Guide.