Hal Murray <hmur...@megapathdsl.net>:
>
> > If dev with merge-approver power pushes to a branch and then merges it, how
> > is the entailed risk any different from a direct push?
>
> We could add a policy that somebody else do the push, presumably after
> checking the code. With details of "check" TBD.
>
> How many of your changes need to actually hit the repo in less than 24 hours?
Depends on whether you think rapidly clearing bugs is important. I do.
I'm really, really reluctant to consent to a policy that increases my
process friction. My experiences with the consequences of that kind of
choice have never been positive.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
