Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

2017-06-20 Thread Victor Stinner
Does it allow catch for 3.3 and 3.4 branches? I got notifications for 3.6, 3.5 and 2.7 backports of https://github.com/python/cpython/pull/1849 but not for the 3.3 and 3.4 backports: https://github.com/python/cpython/pull/2291 https://github.com/python/cpython/pull/2292 These two backports have th

Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

2017-06-20 Thread Mariatta Wijaya
I think it's because there was no 'needs backport to 3.4' label from PR 1849, so it doesn't make the comment about 3.4 backport PR. Mariatta Wijaya On Tue, Jun 20, 2017 at 7:17 AM, Victor Stinner wrote: > Does it allow catch for 3.3 and 3.4 branches? I got notifications for > 3.6, 3.5 and 2.7 b

Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

2017-06-20 Thread Victor Stinner
2017-06-20 16:56 GMT+02:00 Mariatta Wijaya : > I think it's because there was no 'needs backport to 3.4' label from PR > 1849, so it doesn't make the comment about 3.4 backport PR. Oh, I see. These labels don't exist :-) Maybe we should add them, but only security changes should be backported to 3

Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

2017-06-20 Thread Terry Reedy
On 6/20/2017 11:36 AM, Victor Stinner wrote: 2017-06-20 16:56 GMT+02:00 Mariatta Wijaya : I think it's because there was no 'needs backport to 3.4' label from PR 1849, so it doesn't make the comment about 3.4 backport PR. Oh, I see. These labels don't exist :-) Maybe we should add them, I wo