[Doc] update release notes for changes up to cb35f1d #15314

pull harding wants to merge 2 commits into bitcoin:master from harding:2019-02-monthly-release-notes-update changing 3 files +58 −13

harding commented at 2:11 PM on February 1, 2019: contributor

Monthly release notes update. In addition to a few new notes, this removes from the master branch two notes about things that have been backported to the 0.17 branch (though not released yet): unloadwallet RPC now being blocking (0.17 has a detached release note for that) and the PSBT doc (0.17 does not have a release note for that; I'll open a PR).
fanquake added the label Docs on Feb 1, 2019
MarcoFalke commented at 2:31 PM on February 1, 2019: member

this removes from the master branch two notes about things that have been backported to the 0.17 branch (though not released yet)

It is not clear if there will be a 17.2 release (or even at what time), so maybe the release notes should be kept in both branches to serve user that update straight from 17.1 to 18.0 (or users that wait until 17.2 is released)
harding commented at 3:22 PM on February 1, 2019: contributor

@MarcoFalke sounds reasonable to me. So a simple rule for me to follow would be to only remove a note from master if the corresponding feature was actually released in a backport (hopefully with documentation)?
MarcoFalke commented at 3:58 PM on February 1, 2019: member

Yup sounds like a good rule of thumb
Release notes: integrate detached & rm backports 9ad5ca17d9
Update release notes through to cb35f1d3 5d35d4384a
harding force-pushed on Feb 1, 2019
harding commented at 4:21 PM on February 1, 2019: contributor

The two items previously removed because they were backported have been added back and I've updated the OP to describe the current state of this PR.
laanwj referenced this in commit 392d1382c1 on Feb 2, 2019
DrahtBot commented at 3:52 PM on February 4, 2019: member



The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.



Conflicts

No conflicts as of last run.
fanquake commented at 7:12 AM on February 8, 2019: member

utACK 5d35d43
in doc/release-notes.md:119 in 5d35d4384a
```
 115 | @@ -116,7 +116,8 @@ Configuration option changes
 116 |    defaults to being off, so that changes in policy and disconnect/ban behavior
 117 |    will not cause a node that is whitelisting another to be dropped by peers.
 118 |    Users can still explicitly enable this behavior with the command line option
 119 | -  (and may want to consider letting the Bitcoin Core project know about their
 120 | +  (and may want to consider [contacting](https://bitcoincore.org/en/contact/)
```
MarcoFalke commented at 1:46 PM on February 8, 2019:

Shouldn't this link to the public issue tracker?

harding commented at 5:27 PM on February 8, 2019:

I didn't like that the previous text left it unspecified how to contact the project (and, since release notes are posted to the protocol dev mailing list, I was worried people would reply there, which seemed off-topic to me). I chose the website because it lists the following item that seemed like the most appropriate way for individuals and businesses to inform the project about their use of a feature:

For general enquiries and press: contact@bitcoincore.org (not for support).

I think people would be more reluctant to open an "issue" for something that isn't broken (they're using the feature as designed) and which may require business users to publicly describe how they use the software in a toolchain that may produce normally-unrelayable transactions.

However, I don't know who reads the above email or whether they actually want to receive reports about who uses this feature, so I'm happy to switch to the issue tracker if that's preferred.

CC: @sdaftuar (who sought the contact from users of the whitelistforcerelay option)

MarcoFalke commented at 5:45 PM on February 8, 2019:

Thanks for the reply. I think that makes sense and the contact page also links to the GitHub, so they could choose either email or GitHub issue.
MarcoFalke commented at 1:48 PM on February 8, 2019: member

utACK 5d35d43
MarcoFalke merged this on Feb 8, 2019
MarcoFalke closed this on Feb 8, 2019
MarcoFalke referenced this in commit d5dbb45bdf on Feb 8, 2019
DrahtBot locked this on Dec 16, 2021

Contributors

Labels

Linked (view graph)

#15315 [0.17] [Doc] Backport release note about PSBT doc

[Doc] update release notes for changes up to cb35f1d #15314

Conflicts