R. David Murray rdmurray at bitdance.com
Wed May 17 18:59:55 EDT 2017

• Previous message (by thread): [python-committers] Feedback on the new CPython workflow
• Next message (by thread): [python-committers] Feedback on the new CPython workflow
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Wed, 17 May 2017 11:35:29 -0700, Mariatta Wijaya <mariatta.wijaya at gmail.com> wrote:
> It's possible, but remember not all PRs have bpo-issue, eg those with
> trivial label.
> In that case, what should the backport branch be?
> So we might end up with two backport branch name patterns, eg
> `backport-bpo-NNNN-` and `backport-sha1` for the trivial PRs ?

I don't think it is a problem for the bpo issue number to be missing if
there isn't one.  (I presume you meant 'backport-bpo-NNNN-sha1` for the
BPO alternative.)  But how abut using the github PR number in that case?

--David

---

• Previous message (by thread): [python-committers] Feedback on the new CPython workflow
• Next message (by thread): [python-committers] Feedback on the new CPython workflow
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list