IRC meeting summary for 2017-01-19
- Last-minute merges before feature freeze 0.14
- wallet synchronization issues
- Final alert for 0.14
last-minute merges before feature freeze 0.14
#9535 (Split CNode::cs_vSend: message processing and message sending) got some thorough review and would be a great win.
Gmaxwell thinks #9526 (-blocksonly should disable sharing of mempool with dbcache) should be untagged for 0.14. BlueMatt and Sipa think it’s a bugfix and therefor can be merged after the feature freeze.
Priority for 0.14 is solving the nasty remaining issues, like the wallet sync problems.
BlueMatt is fine with untagging #9027 (Unbounded reorg memory usage) for 0.14. It was pointed out we can do a simple fix to address the issue, but there’s other issues making it non-trivial to fix it completely.
- Review #9294 (Use internal HD chain for change outputs (hd split))
wallet synchronization issues
BlueMatt tried to fix issue #9148, but it turned out to be more complicated than anticipated. He recommends #9583 (Move wallet callbacks into cs_main (this effectively reverts #7946)) for 0.14, and do a set of bigger changes for 0.15. His intend for 0.15 is to move these callbacks into a background thread.
- Review #9583 as solution for 0.14
Final alert for 0.14
The bitcoin alert system was a way for trusted parties to broadcast a message to all Core clients about critical network problems. It has been removed in Bitcoin Core since 0.13.0 and has been disabled for a while now.
The final step in the retirement of the alert system is to hardcode nodes to send the final alert to peers to overcome the lack of propagation.
Now is as good a time as any to send the final alert. Given the prior alert there’s no need for delays or announcements.
- Send final alert message (PR #9594)
|wumpus||Wladimir van der Laan|
This summary was compiled without input from any of the participants in the discussion, so any errors are the fault of the summary author and not the discussion participants.