[Twisted-Python] Using Combinator without write SVN privileges? [was: Re: Branch based development]
mary-twisted at puzzling.org
Mon Mar 27 16:32:14 EST 2006
On Mon, Mar 27, 2006, Christopher Armstrong wrote:
> We don't have an actual policy yet on what it takes to get write access
> restricted to sandbox, and branches. We have given access to people on the
> agreement that they only keep their stuff in /branches or /sandbox for a
> while and someone has to review before merging, but this is exactly the
> process we've switched to for everyone now, anyway. It'd still be nice to
> get some access restrictions in place, though.
Is it the case that this should be the default process for everyone and
that something special needs to be done for merging? Andrew might have
already mentioned, but I know that for his project you need to tag
things in your commit message as "r=[reviewer's IRC name]" (or
[trivial]) and that the merging software actually checks this.
We could do something similar, or possibly even stricter where most
"Twisted committers" do not in fact actually have merge capability, only
reviewers do. It depends whether our reviewers are going to be pretty
much all of us who already have access, or some trusted subset.
<skreech> I'm sorry. I forgot that in #twisted, all suggestions are taken seriously.
More information about the Twisted-Python