On Mon, Feb 13, 2012 at 7:00 AM, Veilleux, Jon L <[email protected]>wrote:
> I think that this paragraph is interesting: > > "We were previously using configuration management version control, which > required a lengthy code check-in process," said Clark Dudek, software > developer, IBM Systems and Technology Group. "Rational Team Concert has > encouraged greater code collaboration and better work item tracking within > my team." > > I guess IBM doesn't think they need version control anymore. Might that be > why we are seeing more problems lately? It isn't that they are no longer using configuration management - just different tools with a different world view. In the non-MF world the process involves developers creating their own individual "branch" from a base in a code repository, then working independently on the branches (coding/unit testing etc.) Then, somewhere down the road, they merge their changes into a new base. This offers greater parallelism than in other (let's say "traditional") source management approaches where individual elements are locked while changes are made. It looks terrifying to mainframe folks, but I'm here to tell you it works and there are tools to make it relatively easy. It isn't completely automated - a carbon unit still has to resolve any differences that don't fit, but in most respects there is more freedom and less effort overall. However, as you might imagine, this approach requires great discipline and skill when bringing the pieces back together and that brings us back to the original skills issue that Ed raised. You don't want the B team doing this. -- This email might be from the artist formerly known as CC (or not) You be the judge. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
