diff options
| author | fanquake <fanquake@gmail.com> | 2023-05-19 17:06:15 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-07-25 11:54:02 +0100 |
| commit | 472d6f79b9bf7a714c3672ee88e21483a9a46042 (patch) | |
| tree | 8556480391e519725f900b52f967562b8a87e584 /doc | |
| parent | 5555ecb80ecc1373bc78b3029d1ee33183a9cdc0 (diff) | |
| download | bitcoin-472d6f79b9bf7a714c3672ee88e21483a9a46042.tar.xz | |
doc: remove generate changelog section from release-process.md
We haven't done this since 22.0. It's not clear why dumping out a
version of git log into the release-notes is that useful.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-process.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/release-process.md b/doc/release-process.md index 089203905d..ea1afe7402 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -96,8 +96,6 @@ Open a draft of the release notes for collaborative editing at https://github.co For the period during which the notes are being edited on the wiki, the version on the branch should be wiped and replaced with a link to the wiki which should be used for all announcements until `-final`. -Generate the change log. As this is a huge amount of work to do manually, there is the `list-pulls` script to do a pre-sorting step based on github PR metadata. See the [documentation in the README.md](https://github.com/bitcoin-core/bitcoin-maintainer-tools/blob/master/README.md#list-pulls). - Generate list of authors: git log --format='- %aN' v(current version, e.g. 24.0)..v(new version, e.g. 24.1) | sort -fiu |