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 <victor.stinner@gmail.com> wrote:
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 the same format: title ending with " #2291" and "(cherry picked from commit 90e01e5)" in the description.
Victor
2017-06-16 22:30 GMT+02:00 Brett Cannon <brett@python.org>:
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.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/