Many thanks for the diagrams, Jon. I've been trying to generate something
like these for months and haven't come up with anything but stubs. If the
verbose document isn't proprietary, I'd love to get a copy of it.
Donald.
Jon Hardcastle wrote:
> We operate a similar system here.
>
> All code in the trunk is based from the last system
> test, which has tested feature/bug fixes merged into
> it.
>
> Every single change unless VERY minor is carried out
> in a branch. When development is finished on the
> bug/feature all new changes to the trunk since branch
> are brought into the branch. Conflicts resolved. It is
> then tested (probably just unit/link rather that full
> system). Once it has passed and is properly signed off
> then the feature/bug is merged back into the trunk.
> and then onto any other parallel branches - like
> maintained old versions if it is a bug fix.
>
> The benefit with this approach is the developers can
> commit nightly protecting them against machine
> failure. These commits needn't be compiling as they
> aren't committing to trunk. It also enables us to see
> all the changes for a particular bug/feature as they
> were merged into the trunk in 1 operation. this (in
> theory) makes porting easier.
>
> Find attached some 'dia' generated diagrams. I also
> have a document that describes quite verbosely our
> release process if you are interested.
>
[snip]
--
Donald H Locker
PTM Electronics, Inc
734 426 9010
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-07 13:29:44 CET