On Fri, 16 Jun 2017 at 13:24 Ethan Furman wrote:
> On 06/16/2017 09:48 AM, Brett Cannon wrote:
>
> > Maybe we should amend PEP 11 to say that whomever volunteers to maintain
> a platform
> > must make sure that platform's buildbot is not red for longer than a
> month [...]
>
> How about three?
When you create a backport PR, if the title is formatted as, e.g. "[3.6]
stuff that changed (GH-1234)", then Bedevere will remove the "needs
backport to 3.6" label on the GH-1234 PR and leave a comment linking to the
backport PR that triggered the label removal.
On 06/16/2017 09:48 AM, Brett Cannon wrote:
Maybe we should amend PEP 11 to say that whomever volunteers to maintain a
platform
> must make sure that platform's buildbot is not red for longer than a month
[...]
How about three? Some life changes need more than a month to recover from... (de
On Fri, 16 Jun 2017 at 03:40 Victor Stinner
wrote:
> 2017-06-16 10:37 GMT+02:00 Nick Coghlan :
> > Hopefully reversions will continue to be rare (since relatively few
> > changes are likely to be as platform dependent as PEP 538, and
> > Windows/*nix differences are already covered in pre-merge C
2017-06-16 10:37 GMT+02:00 Nick Coghlan :
> Hopefully reversions will continue to be rare (since relatively few
> changes are likely to be as platform dependent as PEP 538, and
> Windows/*nix differences are already covered in pre-merge CI), but
> when they do come up, the reminder of how to manual
On 15 June 2017 at 23:38, Victor Stinner wrote:
> 2017-06-15 5:31 GMT+02:00 Nick Coghlan :
>> For example, something that would be genuinely helpful would be a bot
>> monitoring PR comments that could automate the "custom-build" dance
>> for core developers (i.e. we'd be able to write something li