On Fri, Dec 8, 2017 at 10:13 AM, Hans HESPEN
wrote:
> Dear Paul & Johan,
>
>
> thank you for your reply. Indeed, 4 eyes principle is like Paul says.
>
>
> The 4 eyes-principle is known for important decisions. Some decisions
> can't be made by a single person, and need to be made by two persons,
On Fri, Dec 08, 2017 at 03:13:41PM +, Hans HESPEN wrote:
> Anyway, Paul has put me on the line of code review tools, post and
> pre-commit. Tools like RhodeCode, Crucible, Rietveld, Collaborator. This is
> actually a bit too much for what I was looking for, but this might be a very
> good alter
mmant
Sent: Friday, December 8, 2017 12:51:38 PM
To: Johan Corveleyn
Cc: Hans HESPEN; users@subversion.apache.org
Subject: Re: 4 eyes priciple on subversion
I think Hans means code review prior to the commit landing in branch that other
people are continually doing 'svn up' from.
If s
I think Hans means code review prior to the commit landing in branch that
other people are continually doing 'svn up' from.
If so, Rietveld, Gerrit specifically enable code review before the commit
lands. Commercial vendors such as RhodeCode an Assembla have code-review
capabilities in their large
On Fri, Dec 8, 2017 at 10:58 AM, Hans HESPEN wrote:
> Dear Subversion enthousiasts,
>
> apart from some issues around the use of changesets, or the use of patches,
> I couldn't find anything on the subject of using the 4eyes priciple with
> subversion.
>
> I would hate to go through the process of
Dear Subversion enthousiasts,
apart from some issues around the use of changesets, or the use of patches, I
couldn't find anything on the subject of using the 4eyes priciple with
subversion.
I would hate to go through the process of stopping to work with subversion and
install something new
