This resolves #11861 (A confusion caused by incorrect information in the release notes).
More information can be found at #11861.
Docs: Remove the ending slashes from RPC URI format. #12112
pull jackycjh wants to merge 1 commits into bitcoin:master from jackycjh:docs/multi-wallet_RPC_interface_correction changing 1 files +2 −2-
jackycjh commented at 2:18 AM on January 8, 2018: contributor
-
Remove the ending slashes from RPC URI format. 2be2b5d58a
- fanquake added the label Docs on Jan 8, 2018
-
promag commented at 11:42 AM on January 8, 2018: member
Do we fix release notes?
-
DuncanBetts commented at 1:19 PM on January 8, 2018: none
I would imagine the intent of release notes is to support a release, by providing accurate information about it. So, my opinion would be that we should. Happy to hear arguments against :).
-
laanwj commented at 1:14 PM on January 11, 2018: member
Normally I'm against changing release notes after a release. They have been copied to many places, in mail, other sites. So it's like closing the barn after the horse left.
But I'm okay with changing this as the examples are really wrong. I'm surprised no one discovered this sooner.
- laanwj merged this on Jan 11, 2018
- laanwj closed this on Jan 11, 2018
- laanwj referenced this in commit 3c6286873e on Jan 11, 2018
-
ryanofsky commented at 1:25 PM on January 11, 2018: member
I'm surprised no one discovered this sooner.
Heh, I'm not surprised by this at all. While we were discussing this change (admittedly, I was against it), I asked repeatedly for documentation to be written to accompany it because I thought the usage was complex and confusing.
I think it's best when documentation and code changes are made at the same time. It prevents mistakes, makes code easier to review, and can even lead to better designs because often writing documentation causes you to look at things from a different perspective.
- DrahtBot locked this on Sep 8, 2021
