Re: Find out which branches exist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> It's less overhead, but it's also a good way to end up with a broken
>> trunk.
>
>
> Er, only if people check broken code into the trunk. I agree that big,
> experimental changes might require branching, but Subversion, for
> example, seems to work fine with everyone checking into the trunk. A
> decent test suite and continuous integration should let you reliably
> check into the trunk.

It really depends a lot on your project's process.

Only committing to the trunk will only work if either:

a) all of the changes are small and incremental, which is a nice goal,
but isn't always practical for many real-world projects.

b) commits consist of multiple distinct changes per commit, which loses
you many of the advantages of using Subversion.

 From my own experiences with using Subversion, I would strongly
recommend using branches liberally for distinct non-trivial development
tasks.

- -Bill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBRx55Swe0AHUdEwQRAhyWAJ0fbMmFsDt13z0/tPAmwTDML9GRBACg1vJd
lzp3DwhRDPH8Q78Aa+JyVA0=
=kDpw
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 14 18:38:58 2004