[python-committers] Wrongly stopping merges discourages merging.
Guido van Rossum
guido at python.org
Mon Jun 4 14:51:27 EDT 2018
+1. For example for mypy I use the "triangular" git setup even though as a
mypy core dev I could simply push my branch to the main repo.
On Mon, Jun 4, 2018 at 11:49 AM, Donald Stufft <donald at stufft.io> wrote:
> I’d also add that it is generally a good thing that people with power and
> a voice (e.g. the core devs) are having a similar experience that an
> external contributor would. This is our best line of defense against the
> external contributor experience degrading to a bad place. By having core
> devs share a similar experience, we can get feedback like the one about
> AppVeyor and try to improve things for everyone, instead of simply giving
> core devs a way to opt out of the pain.
> Sent from my iPhone
> > On Jun 4, 2018, at 1:54 PM, Brett Cannon <brett at python.org> wrote:
> > Please realize that every time we have switched off CI, we have ended up
> with a broken branch, so it's a trade-off between these occasional hiccups
> or occasionally broken branches (and as Victor has pointed out, we are not
> always good as a group about making sure we notice when stuff breaks). Also
> note that because we now have branches that are almost always stable we
> have users who actually run from a checkout directly instead of waiting for
> a release (which also benefits us by helping to surface bugs earlier than
> e.g. an RC).
> python-committers mailing list
> python-committers at python.org
> Code of Conduct: https://www.python.org/psf/codeofconduct/
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers