A standard build based on the default build template will associate changesets and work items to builds.
Recently I got involved in implementing Team Foundation Server 2012 for a large development project.
Once the feature is finished and merged into the main development tree/trunk the changelog files can either stay as they are or be merged into one large file.
Use whatever approach makes sense for your applications, but keep in mind that there are many options available for changelog management.
Using this plugin (and Liquibase in general) adds some structure and process to managing database changes.
It will help avoid inconsistencies, communication issues, and other problems with ad-hoc approaches.
In one build the step took over 2 hours before I cancelled the build, I've been waiting 30 minutes so far on the current build.
This approach makes it natural to maintain the changelog files in source control and also works well with branches.So the change sets "outgoing" from the stream to the snapshot wouldn't be the list you're looking for.Since your change doesn't exist in the stream, it won't show up as outgoing in the report.For example, let’s say you have a DEV-MAIN-LIVE branching hierarchy.Presumably, you’ll work on DEV and do a bunch of checkins.