Philip Hallstrom wrote:
>>> 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!
>
>
I'm almost a little surprised no on has mentioned auto-versioning yet.
Check out
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.developer.webdav.
I set up a separate repository for our sales people to place their
RFP's. So they can work on them, save them, share them, etc. And if
something got changed that shouldn't, we can go in and look at the logs
to find out who did what when (through Tortoise for us tech geeks).
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 23 18:02:45 2006