Re: [Monotone-devel] Re: [RFC] versioned policy -- introduction

[Timothy Brownawell]

On Sat, 2006-09-09 at 20:51 +0200, Wim Oudshoorn wrote:
> SCENARIO I:  Non project leader commits to branch FOO.Stable
> ------------------------------------------------------------
> 
> Expected behaviour:
>          This commit should not by default be visible in the UI,
>          so nobody will by accident check this revision out and 
>          expect it to be a stable version.
> 
>          The commiter either gets a warning and/or can just
>          continue working on the FOO.Stable branch, but nobody
>          will see it.

The committer gets an error, and must give a --force option to make
monotone accept the commit. Nobody will see their commit.

> SCENARIO III: A project leader leaves
> -------------------------------------
> 
> Expected behaviour:
>          The new or remaining project leader can revoke
>          the 'commit' rights to the FOO.Stable branch.  However
>          all certificates handed out by the ex-project leader up to
>          the date he left are still considered valid.
> 
> 
> Problems:
>         
>         Suppose we have in FOO.Stable the following
>         
>         history:  Rev A (VERSION=0.1, signed by: ex-leader, 
>                    |     at that time project leader)
>                    |
>                   Rev B 
> 
>         Now the the project leader leaves and we want 
>         to keep valid the signed Rev A, but not any later revs.
> 
>         Because we can't trust the date certificates it is no use
>         adding a date to the revoke.
> 
>         Suppose now the ex-leader does the following:
> 
>                 Rev A (VERSION=0.1)
>                    |  \
>                 Rev B  \ 
>                        Rev C (VERSION=0.2, signed by now ex-project leader)
> 
>         and synchronizes with our database.
> 
>         If a user does monotone co -r c:VERSION=0.2, what happens?

The control branch has multiple conflicting heads, which is an error
condition. Either the heads will have to be merged, or the users will
have to explicitly choose which one to use.

Tim
-- 
Free (experimental) public monotone hosting: http://mtn-host.prjek.net