Re: Howto: using SVN for QA?

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

On Feb 1, 2005, at 10:09 AM, Benjamin C. Allfree wrote:

> I would like my developers to commit to private sandboxes so I can
> review changes before committing them back into the trunk. Does anyone
> know of a good way to do this?

1) Commit code into the trunk.
2) Make working branches for each project.
3) You check out the current trunk.
4) Merge from their working branch into your working copy.
5) Use svn status and svn diff and other tools to examine changes.
6) When satisified, commit, when not satisfied, don't.

- --
- -- Tom Mornini

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

iD8DBQFB/8eRzaKkuvKwKvcRAgmgAJ977hY31kqFV3wQr3Hcs5v4mxmr0ACgnqPU
ctwzg3szU/VitERQBHf8xBI=
=RK2X
-----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 Feb 1 19:19:10 2005