On 02/22/2017 08:26 AM, Eric V. Smith wrote:
On 2/22/17 7:27 AM, Victor Stinner wrote:
OpenStack happily fixed this issue one or two years ago with "reno":
https://pypi.python.org/pypi/reno
[...]
What do you think of the overall idea?
I'm for it. I'd be interested in hearing what current and former
release managers say.
I'm for it too. Fixing up Misc/NEWS is probably the trickiest and most
error-prone part of cutting a release.
We've discussed this before, somewhere on bpo though I don't have the
issue no. handy. I actually wrote a tool specifically to solve this
problem at the time:
https://bitbucket.org/larry/mergenews
Obviously it's out of date as it's designed to work with Mercurial. I
don't know how such a tool would be integrated into a Git-based workflow.
While I'm sure we can learn a lot by examining "reno", my suspicion is
we'll want our own custom tool. I don't think the hard part is writing
the tool--the hard part is figuring out what we want and how it should
be integrated into our workflow. Actually writing such a tool is easy
and fun, and I'm sure our community would fall all over themselves to
write it if asked. In fact, I'll kind of pre-volunteer to write it
right now, as long as I can write it in Python 3 ;-)
//arry/
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
