On Wed, Feb 22, 2006 at 11:04:24PM -0600, 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 :)
Bust isn't change-commit-test-repeat the same as their current
change-ftp-test-repeat process? At my previous job where we rolled out
version control to both developers and designers, they grumbled about
being forced to use it and how "slow to their process" the
change-commit-test-repeat was .... until they screwed something up and
version control was able to roll back the changes in seconds instead of
hours of recovering by hand. They stopped grumbling :-)
The big thing I found having developers and designers working on web
projects together was that designers weren't comfortable trying to merge
in developer changes. We had to switch to a locking model.
-Christian
--
They sicken of the calm, who know the storm.
-Dorothy Parker
---------------------------------------------------------------------
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:25:56 2006