Contributors mailing list archives


Re: Proposal for new workflow, incorporating "Optimistic Merging"

Leonardo Pistone
- 08/06/2016 10:34:36
Thanks for the initiative Daniel.

One remark: I think an optimistic merge should be blocked by a red
build (and almost nothing else). Otherwise the whole branch becomes
red and CI is worthless, and a huge work needs to be done at the end.
In other words, I think the automated part of the review must stay in
the optimistic version.

On Tue, Jun 7, 2016 at 8:38 PM, Daniel Reis <> wrote:
> Thank you all for the feedback so far.
> I can see that people really have divided opinions on this.
> (OTOH It would be boring if we all agreed on everything :-)
> So, I would like reword my goal for my proposal, stepping back a little:
> The goal would be for a few volunteers to drive an *experiment* with
> optimistic merging, in a couple of selected repos.
> It should keep having stable versions with peer reviews and mandatory
> passing tests.
> Quality of published modules must not be compromised in the process.
> The goal for this discussion would be to draft the process to experiment.
> The process to experiment should be compatible with the current ones, so
> that we can abandon it if we don't like the results.
> This is a tough requirement but I think it is achievable.
> The experiment results would be evaluated after some some (maybe 6 months)
> and could then be killed or expanded, depending on the findings.
> I have a few candidate repos I contribute to:
> - oca/l10n_portugal: very low activity, a few PRs and only two merged
> modules.
> - oca/projects: medium/low activity
> Would this be reasonable?
> Regards
> Daniel
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe: