[Python-Dev] [python-committers] New workflow change: Welcome to blurb (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Sat Jun 24 01:48:01 EDT 2017

On 24 June 2017 at 13:24, Larry Hastings <larry at hastings.org> wrote:

One minor but ongoing problem we've had in CPython core development has been the mess of updating Misc/NEWS. Day-to-day developers may have a conflict if they lose a push race, which means a little editing. You'll have a similar, if slightly worse, problem when cherry-picking a fix between versions. Worst of all used to be the manual merges necessary after cutting a release--this was the bane of a CPython release manager's existence. (Though the new git-based workflow may have obviated the worst of this.) The real problem is that we have one central file that everybody continually edits in a haphazard way. We aren't actually editing the same information, we aren't actually changing the same lines. But our revision control systems and diff algorithms don't understand the structure of Misc/NEWS and so they get confused. And for what? It's not like there's a tremendous benefit to having this central file everyone's fighting over. We've been talking about addressing this for years. Fixing this was one of the goals of the new workflow. And finally, as of right now, the future is here. Ladies and gentlemen, I present: blurb. https://github.com/python/core-workflow/tree/master/blurb

Thanks Larry, great to see this go live!

Behind the scenes, blurb writes your information here:

Misc/NEWS.d/next// The "" is the name of the section in Misc/NEWS where your entry should go. contains the current date and time, the bpo number, and a nonce to prevent collisions.

Folks are also free to handcraft these files if they really want to do so. The Developer Guide has the necessary details: https://docs.python.org/devguide/committing.html#what-s-new-and-news-entries

Cheers, Nick.

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

More information about the Python-Dev mailing list