On 12/9/20 11:19 AM, Ethan Furman wrote:
Greetings!
I'm hoping somebody can alleviate my confusion. I had thought that
the blurb tool was created to resolve the near-constant push races
when the NEWS file was updated; but it appears that it only affects
the change log.
NEWS /is/ the changelog. The "changelog" you see on the web site, e.g.:
https://docs.python.org/3/whatsnew/changelog.html#changelog
is basically the NEWS file run through "rst2html".
If I have a change that really needs to be in the NEWS file itself, do
I need to directly edit that file?
a) No. Run "blurb" as normal to add your change.
b) You can't anyway. NEWS is no longer checked in.
The process is: when you run "blurb", it adds a file containing that
text to "Misc/NEWS.d/next". Then, when the release manager makes the
next release, they'll run "blurb release", which merges all those
individual text files into one big version-specific aggregate file of
news blurbs stored in "Misc/NEWS.d/<version_number>.rst". Finally, when
the release manager builds the source distribution (for tarballs etc),
they run "blurb merge", which merges all the
"Misc/NEWS.d/<version_number>.rst" files together into one big glorious
NEWS file. "Misc/NEWS" is no longer checked in, it's generated on
demand using "blurb merge".
//arry/
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/BE5RK35TZG5H5QZSJMMHBOVVLOU3KNGE/
Code of Conduct: http://python.org/psf/codeofconduct/
