Hi, I would prefer C-T-R (commit, then review), because it reduces bureaucracy. Except for changes just before a major release (when there is little time to und or change things).
+1 to [REVIEW] emails. In my view, this should include new configuration and new features. Basically all "important" user-visible behavior changes. Sure, it's hard to say what is important and what is not. Regards, Thomas On 20/10/16 14:21, "Bertrand Delacretaz" <[email protected]> wrote: >On Thu, Oct 20, 2016 at 2:02 PM, Michael Marth <[email protected]> wrote: >> ...So I have a proposal: when a new public API is added the developer >>should drop an >> email with subject tag [REVIEW] onto the dev list, so that others are >>aware and can >> chime in if needed... > >The Oak team can also just decide that new APIs are to be handled in >R-T-C mode instead of C-T-R. > >It's kind of the same thing but using standard Apache terminology ;-) > >-Bertrand
