[Seaside] working in teams..

[Sean Allen]

On Oct 24, 2008, at 5:19 AM, Philippe Marschall wrote:

>> what is the mechanism?
>
> SVN for CSS / images / JS.
>
> Monticello (local http repository) for Seaside code.

can someone explain exactly why this is the way you would want to do it?

if you need to keep css, images etc in sync with smalltalk code,

tagging, branching etc then this seems like a non starter.

what do you really gain from the 2 repo split?

how do people work around it?

do you check monticello packages into svn when branching, tagging etc is
done to keep everything together in one place?

just not worry about it from the tech side and use a 'human solution'?