Re: Best practices for getting non-tech folks to use subversion?

>> Using Subversion, as you say, you commit once your code is done and tested.
>> But in this scenario it cannot be tested until the code is on a server; it
>> cannot be tested locally (see below).
>>
>>
> No, you commit to the development branch once you are satisfied that your
> changes look ok and it is time to test. Then you test by pulling up the
> testing vhost on the server in your browser.

The problem is that designers can't even see if things "look ok" without
putting the files on the vhost first. No way they will make a blind
change, commit it, test it, repeat. They just won't :)

I think we're just talking about different stages in the development.

Ryan's solution of samba/tortiose sounds like it's the best option for me
at this point.

Thanks all!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 23 06:04:11 2006