Re: When to Commit: Perishable Value and Durable Value
- --- In firstname.lastname@example.org, Jim Hyslop <jhyslop@d...> wrote:
> Greg Akins wrote:Indeed. That was where the bkog-entry in question had mentined the
> > I don't want to answer for Brad, but private line
> > commits would provide insurance without "decreasing"
> > the value of the main codeline.
"Private Versions" pattern which does exactly this :-)
> I'd agree with that. As long as the private line is frequently updatedpainless.
> with changes on the main codeline, so final merging is quick and
A great big "Yes" to that too. The pattern is called "Workscape
Update", and there is a follow-up to it in a paper that is
separate from the book:
* /Codeline Merging and Locking: Continuous Update and Two-phased Commits/
The paper also deals with several different patterns for
synchronous/serialized commits, including: single integration point,
integration token, and about a half-dozen other mechanisms.
And if you're interested in that, you might also be interested in:
* /Continuous Staging: Scaling Continuous Integration to Multiple
Brad Appleton <brad@...> www.bradapp.net
Software CM Patterns (www.scmpatterns.com)
Effective Teamwork, Practical Integration
"And miles to go before I sleep" --Robert Frost