Sign in
Bill Heys - VS 2010, ALM, TFS, Branching and Merging, and all that
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Tags
Agile
Best Practices
branches
Branching
Bug Fix
C#
Cherry Picking
Compression
Conchango
Deltafication
Dependencies
Feature Splitting
Feature Teams
Features
folders
German
Glossary
Guidance
GZip
Hotfix
Linq
Merge
Microsoft
MSDN
MSDN Magazine
Multiple Release
Ranger
Rangers
Relative References
Renaming
Reverse Deltas
Role Security
Scrum
Service Pack
Servicing
Shared Code
Shelvesets
Software Update
Source Control Management
Spanish
Sprint Backlog
Team Foundaton Server
Team System
TFS
TFS Branching
TFS Integration
TFS Migration
Time Boxed Sprints
Version Control
Visual Studio
VS 2010
VS ALM Rangers
VS2010
VSTS
VSTS 2008
VSTS 2010
vsts 2010s
VSTS Rangers
VSTS VS 2010
VSTS2010
Browse by Tags
MSDN Blogs
>
Bill Heys - VS 2010, ALM, TFS, Branching and Merging, and all that
>
All Tags
>
hotfix
Tagged Content List
Blog Post:
Isolating and Integrating Parallel Feature Teams working on Separate Overlapping Releases
Bill Heys
Customer scenario: How should I isolate (and integrate) changes when working with: 3 parallel efforts (two parallel development efforts, working on separate releases of the product and production support) Production(version 2.0) with the need to issue hotfixes on then current production version Development...
on
23 May 2011
Blog Post:
How do I create bug fixes for EVERY version of a product EVER released
Bill Heys
A customer asks the following question: “ We are building factory machine. New machines are usually delivered with the current stable software version. We don't do regular updates because our customers prefer stability over new features. After reading the Rangers Branching Guide I have some questions...
on
5 May 2011
Blog Post:
Where do I fix a production defect?
Bill Heys
Question from a customer of the Rangers Branching Guidance ( http://tfsbranchingguideiii.codeplex.com ) “My company has a major release every 3 months. In between major releases we have monthly maintenance releases. (Similar to the "Advanced Branching Plan") Our monthly release usually...
on
22 Mar 2011
Blog Post:
Parallel Feature Teams working on multiple releases in development. Monthly releases to production.
Bill Heys
I recently received a question from a customer who is dealing with the need to support multiple feature teams working on multiple releases in development. They asked how to structure branching to support this environment. Background: My company is, for all practical purposes, a dot com. We have a single...
on
14 Jan 2011
Blog Post:
Basic Branch Plan–Where to fix a bug in my release?
Bill Heys
Question from Customer: In the single team branch, once a release is done and if a bug is reported are we supposed to fix the bug in the Main branch and forward integrate back to the DEV branch Response: Separating Development from Release, bug fixing a shipped release is a Release question, not a question...
on
22 Dec 2010
Blog Post:
Question on the Basic Branching Model
Bill Heys
Question from customer: “I am very new to this branching concept and try to understand. I am not able understand the difference between the Single release vs. single team branching. Can someone help in knowing the difference.” Response: I like to think of branching for development separately...
on
22 Dec 2010
Blog Post:
Supporting Multiple Feature Teams, Multiple Development Cycles and Multiple Releases in an agile way
Bill Heys
In answer to the following question: “Are you advising that we wait until the build on Main is stable and all dependent systems are ready before we attempt to deploy anything? This makes a hard-to-hit-target nearly impossible to hit (we have multiple teams, so it is already complex as it...
on
9 Dec 2010
Page 1 of 1 (7 items)