Creating a drop folder

I am working on a project where the clients wants to be able to
download the "builds" (or "drops" as we call them) directly from the
repository. I'd rather they not have access to all the daily updates
the programmers do, or have access to versions that happen between the
agreed upon drop dates.

My solution that to create a drop branch in the repo:

myproj/trunk
myproj/drop

and give the client read-only access to only myproj/drop

Then, when a drop was due, I can just merge the /trunk into /drop. If
there are any little fixes that need to be down right after the drop,
I just do another quick merge.

Is this the best way to do this?

My problem is that I can't seem to get it to work. It never seems to
want to merge. If new files are created in /trunk, the merge just
complains. Shouldn't the merge be able to create/copy the new files
in /drop?

I need this to be a 100% automated process. Since /drop is read-only
by the client and I will only be merging from /trunk, there should
never be any conflicts.

Am I thinking about this the right way?

Tankko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 13 18:14:14 2006