Newsletters: add #13 (2018-09-18)

[harding]

Todo:

• Optional: add Dashboard Items section (@moneyball)
• Maybe describe Bitcoin Core 7965 given this week's merge of 14168? See note in the Notable Merges section tagged TODO. In any case, remove the TODO note. (@jnewbery)

[moneyball]

I gave it a quick read and looks good to me.

…

On Mon, Sep 17, 2018 at 2:14 AM David A. Harding ***@***.***> wrote: Todo: - Optional: add Dashboard Items section ***@***.*** <https://github.com/moneyball>) - Maybe describe Bitcoin Core 7965 given this week's merge of 14168? See note in the Notable Merges section tagged TODO. In any case, remove the TODO note. ***@***.*** <https://github.com/jnewbery>) ------------------------------ You can view, comment on, or merge this pull request online at: #67 Commit Summary - Newsletters: add #13 (2018-09-18) File Changes - *M* _includes/references.md <https://github.com/bitcoinops/bitcoinops.github.io/pull/67/files#diff-0> (2) - *A* _posts/en/newsletters/2018-09-18-newsletter.md <https://github.com/bitcoinops/bitcoinops.github.io/pull/67/files#diff-1> (175) Patch Links: - https://github.com/bitcoinops/bitcoinops.github.io/pull/67.patch - https://github.com/bitcoinops/bitcoinops.github.io/pull/67.diff — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAT6A7170NHsv0MsxSojl4DI_yMjdDZ_ks5ub2ffgaJpZM4Wrhl2> .

[jnewbery]

ACK e89c9fb. I've added a new commit that:

• describes bitcoin core issue 7965
• softens the language around removing P2P reject messages.

I plan to send the newsletter out at ~9 eastern tomorrow. If anyone has the chance to review before I send it, it would be appreciated!

[harding]

8d52f86 text LGTM.

I've added information to the newsletter about the security release of Bitcoin Core 0.16.3.

[jnewbery]

ACK 9dc561d

[ryanofsky]

In the future could link to bitcoin/bitcoin#10102 when referring to multiprocess stuff, since that's where the implementation is. TBH though bitcoin/bitcoin#7965 doesn't actually have much (or anything?) to do with testing or process separation.