From: Peter Dimov (pdimov_at_[hidden])
Date: 2007-06-11 13:19:15
> on Fri Jun 08 2007, troy d straszheim <troy-AT-resophonic.com> wrote:
>> On Wed, Jun 06, 2007 at 08:40:52AM -0400, David Abrahams wrote:
>>> I've been asking myself why we're still talking about a "trunk,"
>>> too. Can somebody explain why, and what it's supposed to mean?
>> So to talk about the 'trunk' in a CVS-less environment is to either
>> be vague or to imply that the development process is CVS like.
I'll try to give a hopefully non-vague answer reflecting my idea of 'trunky'
The trunk is where integration testing happens. If the testing resources can
only cover one branch, the trunk is that branch.
Development occurs on the trunk via incremental refactoring. Ideally,
changes are committed only after a test cycle, so that the reason for a
regression can be isolated with reasonable accuracy. The practice of a
developer working on a branch (or on the local copy) for four months, then
merging a major patch and breaking the world is discouraged. The practice of
a developer working on a branch for four months and then not merging at all
because the real world interfered in the meantime is discouraged.
Non-incremental development is discouraged.
Does this make sense? :-)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk