Removes these two paragraphs that were part of the 0.18.0 release notes but which I don't think need to be repeated for the 0.18.1 release notes. The systemd release note in particular links to a section that isn't part of the document.
[0.18] Doc: remove old release notes about systemd and riscv changes #16532
pull harding wants to merge 1 commits into bitcoin:0.18 from harding:2019-07-0.18.1-release-notes changing 1 files +1 −14-
harding commented at 3:48 AM on August 2, 2019: contributor
- fanquake added the label Docs on Aug 2, 2019
- fanquake added this to the milestone 0.18.1 on Aug 2, 2019
-
Doc: remove old release notes about systemd and riscv changes 5f5b444cc0
- harding force-pushed on Aug 2, 2019
- fanquake approved
-
fanquake commented at 6:19 AM on August 2, 2019: member
ACK 5f5b444cc02190352312021c736d88c925731d90 - this should be fine.
The
major->minorversion change is correct. -
MarcoFalke commented at 12:16 PM on August 2, 2019: member
ACK
-
practicalswift commented at 4:59 PM on August 2, 2019: contributor
ACK 5f5b444cc02190352312021c736d88c925731d90
-
MarcoFalke commented at 5:03 PM on August 2, 2019: member
@laanwj Could merge this and then kick off the release?
After those, if needed: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-every-release-candidate
-
jonatack commented at 5:36 PM on August 2, 2019: member
ACK. For the future, is there a procedure to follow for adding commits missing from the release notes and credits? I thought it happened automatically but seems not (minor example 194226f6798e59cfd871db0335e078101b165043 that dropped through the cracks in 0.18.0 and here).
-
jonatack commented at 5:40 PM on August 2, 2019: member
@laanwj Could merge this and then kick off the release?
After those, if needed: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-every-release-candidate
FWIW the release process updates are in master only and not in the tagged releases 0.18.0 and 0.18.1.
- laanwj merged this on Aug 2, 2019
- laanwj closed this on Aug 2, 2019
- laanwj referenced this in commit 673919caf7 on Aug 2, 2019
-
laanwj commented at 8:21 PM on August 2, 2019: member
After those, if needed: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-every-release-candidate
hm that's a good point actually, we need a "pre-release" release process
what you linked is the process for release candidates, not for releases, the release itself is not a candidate
e.g. doing a translations update from transifex now would, in principle, require a new round of testing, so would any other change that affects the binary
the only thing alllowed to do now is set
_CLIENT_VERSION_RCto 0 (…which does affect the binary too, but hopefully only in a minimal way…) and change documentation such as manpages - laanwj referenced this in commit 9ad4f22a20 on Aug 9, 2019
- DrahtBot locked this on Dec 16, 2021