Re: [Codestriker-user] Feature request

[David S. <si...@us...>]

> Hi David,
> 	Just FYI, we don't do development this way, nor does any
> development organization that I've been a part of for the last 20 years.
> We do projects in branches, have the branches reviewed, do unit test,
> THEN merge it to the main line of development.  We want our developers
> to be able to do a commit at any time (and urge them to do it at least
> daily) to prevent mishaps due to power outages, drive failure, etc.
> This has paid off more than once!  The other issue arises when you're
> working on a change that affects several different platforms (aix,
> solaris and windows for instance), you need to be able to commit, so
> that you can check the code out on the other machines to do unit
> testing.

Hi Kelly,

I guess the key message here is that with your process, each developer has 
their own separate _private_ branch, so even if they do daily commits to 
their private branch, there is no impact to the rest of the development 
team.  With your process, there is still a way once the work has been 
completed, to generate a diff that can be reviewed, and then merged with 
the main branch.

With the process described by Matthew, unreviewed code from more than one 
developer is being committed into a branch/main trunk, which I think is a 
big problem.

The basic message is unreviewed code should never be committed to a 
"public" branch that other developers are using.

-- 
Cheers,
David