
Distributed Version Control Systems in the Enterprise
Every major Open Source project worldwide has already embraced Distributed Version Control Systems (DVCS), will enterprises be next?

Every major Open Source project worldwide has already embraced Distributed Version Control Systems (DVCS), will enterprises be next?
Due to overwhelming demand, CodePlex is now offering Git for source control. Git is the third source control system available for CodePlex hosted projects, the first two being TFS and Mercurial.
The Eclipse Foundation has made Gerrit available for projects using the Git version control system at https://git.eclipse.org/r/. This allows patches to be sent directly in the form of commits which can be applied to a Git repository, although the Eclipse IP Process needs to be updated to make it widely useful. Read on to find out what this means for Eclipse projects.
The number of projects using Git has passed the number of repositories using SVN at Eclipse, making Git the single most popular version control system for Eclipse projects. InfoQ takes a look at the numbers, and the increasing number of DVCS repositories used by foundations and hosting providers.

The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.

There has been a lot of conversation going on around the configuration of applications, and how to manage it. This article explores things people can do from within their code to make their lives, and the lives of anyone else who has to administer or maintain their application, easier. These patterns have been used a number of times on ThoughtWorks projects, and they have proven their worth.

Today we introduce the book “Web Service Contract Design and Versioning for SOA” by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, L. Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley. More exactly, chapters 20, 21, and 22 of the book addressing the issues related to service contract versioning.
Ryan Slobojan discusses how to perform issue tracking, code review, commits and builds in an automated manner by integrating Git, Gerrit, Hudson and Mylyn.
Scott Chacon explains the internal mechanisms used by Git to do version control based on three trees –head, index, work–, and some of its commands, especially ‘reset’.

Software developers spend a lot of their time working in an IDE or editor. JetBrains Tool Evangelist Hadi Hariri talking about expanding IDE offerings, Jetbrains Open-Source experiences and community contributions, Objective-C and dynamic language IDE's, tool integration and a sneak preview into the future of software development.

InfoQ sits down with Andrew Hunt, one of the original Agile Manifesto signatories, to discuss how Agile has diverged from the original vision and how pragmatic programming has evolved. Andy discusses CoffesScript, Arduino, and HTML5 and he shares his views on the effectiveness of pair programming, Agile testing methods and other practices.

This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.