On 10/1/06, adam@londonbaby.com.au <adam@londonbaby.com.au> wrote:
>
> Developers in my department work as follows:
>
> 1) All development & testing occurs on an intranet server.
> 2) One project directory (on the intranet server) is shared by all developers.
> 3) This same directory is used by IIS as the local version of a web project.
> 4) Nothing is done on a developers local machine.
> 4) All changes to a project good or bad are instantly viewable by the
> dev team & management.
>
> With the implementation of subversion the developers want to work in
> pretty much the same
>
> way. So I am trying to figure out how to emulate this environment with
> subversion.
>
> Then there is the option of sharing a working copy of a project, but i
> don't think you can
>
> do that???
Technically you can share a working copy between developers, but
you're negating much of the reason for using a version control system
in the first place if you do so. Developers will still clobber each
others' changes, and will almost certainly Developer A will at some
point check in Developer B's changes which aren't ready to be checked
in.
> My final thought then is the option of creating one working copy of a
> project which can be
>
> used as the main project directory (powering the intranet).
>
> Then individual developers can check out their working copies of a
> project, make adjustments
>
> and commit changes to the repository. This in turn invokes a hook
> script that updates the
>
> working copy powering the intranet.
That's the normally-recommended setup.
> The problem with the last item is, because developers won't be testing
> locally having to
>
> perform a commit just to view the progress of their work on the
> intranet could cause
>
> astronomical version control numbers and repository database sizes;
> and might be a tad
>
> ridiculous in implementation.
>
> We are working on a windows intranet server!!!
High revision numbers: who cares? It's just a number.
Large repository size: do you regularly change large binary files?
Ridiculous implementation: why?
> Would love any input, on how i can implement subversion to acheive the
> required results.
>
> Is it possible?
>
> If not, what must we do to get around any hurdles.
Have every developer capable of running the website/project on their
development machine. This may sound odd to you, but it's a better way
of doing things. IIS comes with WinXP and Win2000 Pro, so technically
this shouldn't be a problem. Each developer works from his/her own
working copy, and when happy with their work, checks everything
they've done into the repository. Your hook script then updates the
server for everyone to see.
As a developer, I want to have a place to check out any changes I do
before anyone else sees them. You say that you want changes
"immediately" available for both developers and management. I don't
like showing incomplete stuff to managers - they tend to get nervous
about the state of the project.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 1 20:52:49 2006