On Friday 16 February 2007 10:01, Jan Hendrik wrote:
> > 1. Each developer must have their own svn WC (subversion working
> > copy). I still saw no reason why you cannot each have, on your
> > own PC, an svn client which can be secured just as much as any
> > other form of file transfer.
>
> They have, each on their own PC, one of the PCs also acting as
> SVN server for the repository.
>
> It's the production webserver that is completely out of reach for
> SVN and that we have to get stuff synched onto via FTP.
Really, this is the part which did not make sense. You mean each
person does have svn client on their PC (that is what I thought you
were saying is not possible)? If each person's PC does have svn
client, no need for the problem you say you are having. Update
whatever website from subversion repository. The path of FTP sync
should only be between an export (from that repos) and the web
server, so not interfering with checkins. Sorry, I probably sill
have touble visualizing your whole environment.
> > 2. Each developer should only check out the part of the project
> > they are working on. At least I have never seen a project where
> > each member of the team must constantly work on 10,000 files at
> > once. They have always been broken up into categories (by subdir)
> > so that one week I might be working only on the "drivers/wheel"
> > component.
>
> We are not doing development, but web content (catalog of stock
> items). That's kind of different workflow. And we do this just
> for own needs. Although it is broken up into categories 2-3 levels
> deep they all are more or less loosely bound to each other. Usually
> there is nothing I would work on for a week or even a day either,
> and usually there happens to be a cross-link necessary here and
> there. We would spend our days checking out & in and making tons
> of notes for links to be set after the next checkout of this or
> that category. :)
Think more abstractly. We certainly "develop" websites just as much
as we develop software. Without development your website would
never... well... develop :) [http://m-w.com/dictionary/develop ]
I'm not certain anymore where you are conflicting with subversion
and FTP I don't see the need to do it. I will look back at your
other descryptions because it must have been explained. There just
should never be need for an svn working copy which also syncs
through FTP or rsync to another place. Everyone syncs their work
using only svn, then their individual changes can be tested from
another export or sync with the repository. Repository is therefore
the central point of syncing.
== Simple Creative Example ==
I `svn checkout $BRA/cgi/splat.py` (not the whole 15,000 files)
sally has already been working on $BRA/cgi/upd.py
I edit splat so that it uses proper syntax when calling 'upd'
sally `svn commit upd.py -m"added a parameter for integrity"`
I `svn commit splat.py -m"send correct number of parameters to upd.py"`
We look at the internal test site and see how our changes work out.
I notice that my change didn't work because upd still says wrong #
parameters. I scold sally for not telling me she was changing that
again. Of course fixing the problem again, I see it all work on the
test site.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 16 21:58:21 2007