Re: Help with "multiple level" repositories for a newbie

[Andrew Johnson]

Borja Pardo wrote:
> 
> We want to have two different levels in repositories. Let me explain: we
> want a repository ( a "working copy repository") where every programmer can
> perform updates, commits, etc. Then, a project "integrator" checks if
> everything is OK with the changes and performs these changes in a second
> level (or "main") repository. He is the only one who can make changes in the
> last repository. This is to assure things in the main repository are correct
> changes.

We have a related approach which involves using 2 repositories.  One is
used for every-day working copies, until we come to a release point when
everyone checks their work individually and we run various tests.  At that
point we tag that repository and use cvs export to generate a release
tree.  This release is cvs imported into another repository that is used
for operational software, and isn't writable by the same group of people,
using Unix permissions to enforce that.

You might need to move the operations around a little bit, but the
approach works Ok for us and isn't that hard to manage.  You could even
automate parts of it with a few scripts if so inclined.

- Andrew
-- 
Perfection is reached, not when there is no longer anything to add,
but when there is no longer anything to take away.
- Antoine de Saint-Exupery