Your decision to not read what's considered the definitive book on continuous development by the person considered the biggest expert.

But CI processes I recommend are totally aligned with DVCS. If not, I wouldn't recommend them to companies using DVCS.

BTW, authors can't afford cheapskates.

>Thanks for the proposal Craig, but I prefer free reading. Can't afford the money for every published book.
>
>My work style is more aligned as Git docs, like the really good links that Hank Fay posted (Thanks Hank!). *This* is decentralized working. All in trunk is not decentrilized working, and is for old SCM style working, not DVCS style working. If you use DVCS is because your team can be geaographically distributed,and not all together in same room or same office.
>
>If you think about it, branching is something more natural, but for those who never tried simulataneous development with good practices for *this* model of work, then can be some difficult to understand it. You simply can't afford parallel working with "all in trunk" work style, because this is anti-pattern relative to parallel working.