Right now I'm only using the cherry-pick labels to verify whether a
backport has been done or not, so then I can remove the `needs backport to`
label from the original PR.
If all of these become automated, then perhaps cherry-pick labels aren't
needed.
There should still be a bot that removes the
On Tue, 9 May 2017 at 10:23 Mariatta Wijaya
wrote:
> Right now I'm only using the cherry-pick labels to verify whether a
> backport has been done or not, so then I can remove the `needs backport to`
> label from the original PR.
>
Sorry, I didn't mean to suggest that I thought the "needs backpor
As another note, PEP 545 (https://www.python.org/dev/peps/pep-0545/)
requires a lot of changes to how Python generates its documentation.
RTD already has support for this
(http://docs.readthedocs.io/en/latest/localization.html) and I'd argue
this is another classic case of duplicating effort, inste
On 10 May 2017 at 03:23, Mariatta Wijaya wrote:
> Right now I'm only using the cherry-pick labels to verify whether a backport
> has been done or not, so then I can remove the `needs backport to` label
> from the original PR.
For that purpose, what's probably more important is the backport PR
tit
Eric Holscher wrote:
As another note, PEP 545 (https://www.python.org/dev/peps/pep-0545/)
requires a lot of changes to how Python generates its documentation.
RTD already has support for this
(http://docs.readthedocs.io/en/latest/localization.html) and I'd argue
this is another classic case of
