[Python-Dev] New workflow change: Welcome to blurb

Nick Coghlan ncoghlan at gmail.com
Sun Jun 25 02:44:55 EDT 2017

On 25 June 2017 at 16:31, Terry Reedy <tjreedy at udel.edu> wrote:
>> 25.06.17 06:04, Nick Coghlan пише:
>>> All the PRs share an issue number in that case, so Bedevere should be
>>> able to pick up that there's a pre-existing NEWS entry (even if it
>>> isn't being added by that particular PR).
> You seem to be suggesting adding a possibly incomplete entry with the first
> patch.  If that is so, it would be helpful if blurb could pull an existing
> file for an issue into the editor.

I was mainly referring to cases where either an initial commit (with a
complete NEWS entry) requires follow-up fixes (no NEWS edit

However, another case did occur to me, which is fixing bugs reported
against never-released features (which is what I'm currently working
on for PEP 538).

So trying to automate that particular check may end up proving to be
more hassle than it's worth.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list