Re: Commit - Approve cycle ?

Quoting Helge Jensen <helge.jensen@slog.dk>:
> Sorry to "barge in" on this discussion, I'm not entirely sure I
> understand the discussion, but it sounds to me like a search for a
> workflow that supports "approval" of commits.
>
> Couldn't this be solved with a simple way of working? without having
> commits "suspended".
>
> 1. copy from where you wish to commit to some other place.
> 2. while !done
> 2.1 edit
> 2.2 commit
> 3. start the approval procedure giving it the path where you copied
> to as input, and a description of what has changed.
>
> the approval procedure can:
>
> 1. merge current trunk (or whatever) with the changes
> 2. compile, test, ..., do manual edits and whatnot
> 3. commit or reject, giving feedback to requester of approval
>
> If the approval procedure is entirely automatic it should be no
> problem to automate the whole procedure.

A thread about approvals from a few months ago triggered a similar idea in my
head: http://svn.haxx.se/users/archive-2005-05/0536.shtml

Apparently no one else thought it was a useful idea, as there were no other
replies.

-- 
Andrew Thompson
http://aktzero.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org