|
| 1 | +--- |
| 2 | +title: IRC meeting summary for 2018-06-07 |
| 3 | +lang: en |
| 4 | +permalink: /en/meetings/2018/06/07/ |
| 5 | +name: 2016-06-07-meeting |
| 6 | +layout: page |
| 7 | +type: meetings |
| 8 | +version: 1 |
| 9 | +--- |
| 10 | +{% include _toc.html %} |
| 11 | +{% include _references.md %} |
| 12 | + |
| 13 | +- View this week's log on [BotBot.me](https://botbot.me/freenode/bitcoin-core-dev/msg/100892716/) or [MeetBot][mb log] |
| 14 | +- [Meeting minutes by MeetBot](http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-06-07-19.00.html) |
| 15 | + |
| 16 | +--- |
| 17 | + |
| 18 | +Topics discussed during this weekly meeting included a quick update on |
| 19 | +the progress of the next maintenance release, what pull requests members |
| 20 | +of the project would like reviewers to focus on during the upcoming |
| 21 | +week, and finding a better way for Bitcoin Core to internally keep track |
| 22 | +of command line parameters. Also some side discussion about optimizing |
| 23 | +code for various computer processor architectures. |
| 24 | + |
| 25 | +## 0.16.1 release progress |
| 26 | + |
| 27 | +*This was not an announced topic, but it was briefly discussed before |
| 28 | +other topics.* |
| 29 | + |
| 30 | +Wladimir van der Laan announced the tagging of the second release |
| 31 | +candidate for version 0.16.1, asked [Gitian][] builders to generate |
| 32 | +signed checksums, and said, "I hope this can be[come] the final |
| 33 | +[version] very quickly." |
| 34 | + |
| 35 | +## High priority for review |
| 36 | + |
| 37 | +**Background:** each meeting, Bitcoin Core developers discuss which Pull |
| 38 | +Requests (PRs) the meeting participants think most need review in the |
| 39 | +upcoming week. Some of these PRs are related to code that contributors |
| 40 | +especially want to see in the next release; others are PRs that are |
| 41 | +blocking further work or which require significant maintenance (rebasing) |
| 42 | +to keep in a pending state. Any capable reviewers are encouraged to |
| 43 | +visit the project's list of [current high-priority |
| 44 | +PRs][]. |
| 45 | + |
| 46 | +**Discussion ([log][log hipri]):** the following pending PRs were |
| 47 | +mentioned this week: |
| 48 | + |
| 49 | +- **[#12196][]:** Add `scantxoutset` RPC method. Previously on the list. |
| 50 | + |
| 51 | +- **[#13062][]:** Make script interpreter independent from storage type. |
| 52 | + Previously on the list. |
| 53 | + |
| 54 | +- **[#11082][]:** Add new bitcoin_rw.conf file that is used for settings |
| 55 | + modified by this software itself. Previously on the list. The author |
| 56 | + of the PR, Luke Dashjr, had some concerns that were discussed as a |
| 57 | + separate topic later in the meeting. |
| 58 | + |
| 59 | +- **[#12136][]:** Implement BIP 174 Partially Signed Bitcoin |
| 60 | + Transactions. Previously on the list. Wladimir van der Laan noted |
| 61 | + that this had lots of active discussion in the last week. The author |
| 62 | + of the PR, Andrew Chow, said that it and its [associated BIP][BIP174] |
| 63 | + still needs more review. Pieter Wuille added, "I've also been |
| 64 | + discussing some ideas for splitting part of it up." |
| 65 | + |
| 66 | +- **[#13111][]:** Add `unloadwallet` RPC. Previously on the list. Van der Laan |
| 67 | + said it "should be pretty close [to being merge-ready]." |
| 68 | + |
| 69 | +There was also some discussion of processor-specific optimizations and |
| 70 | +tests being written and run primarily by Pieter Wuille and Cory Fields |
| 71 | +with several other developers assisting with testing on specific |
| 72 | +hardware platforms. These were related to SSE4, SSSE3, SIMD, and AVX. |
| 73 | + |
| 74 | +## Command line argument mapping |
| 75 | + |
| 76 | +**Background:** as discussed in a [previous meeting][rw conf meet |
| 77 | +notes], several contributors are working towards creating a |
| 78 | +machine-writeable configuration file that will be shared between Bitcoin |
| 79 | +Core's daemon and GUI so that when users change a setting in one |
| 80 | +program, it'll be set the same way in the other program. |
| 81 | + |
| 82 | +**Discussion ([log][log cli args]):** Luke Dashjr requested the topic |
| 83 | +and introduced it by describing a [recent change][#11862] to how Bitcoin |
| 84 | +Core handles startup parameters. "The change complicates how to |
| 85 | +implement [a machine-writeable configuration file]." |
| 86 | + |
| 87 | +Several developers said that they didn't understand the interactions |
| 88 | +well enough to comment on the matter, with Pieter Wuille saying, "I feel |
| 89 | +like the right people aren't here to discuss that." |
| 90 | + |
| 91 | +John Newbery said the change in question "added really good code |
| 92 | +coverage [...], so it should be pretty straightforward to follow." |
| 93 | + |
| 94 | +**Conclusion:** it was suggested that Dashjr contact a developer with |
| 95 | +more knowledge who wasn't in the meeting, inspect the currently |
| 96 | +available tests, and ideally write more tests to ensure proper behavior |
| 97 | +before making any significant changes. Dashjr agreed, "sounds like |
| 98 | +either way I should start with tests." |
| 99 | + |
| 100 | +## Comedic relief |
| 101 | + |
| 102 | +{% highlight text %} |
| 103 | +<wumpus> I do not have the capacity to pay attention to |
| 104 | + all PRs in parallel |
| 105 | +<promag> really? :P |
| 106 | +<sipa> we need to have an AVX2 wumpus |
| 107 | +<wumpus> sipa: +1 |
| 108 | +<sipa> +8 |
| 109 | +{% endhighlight %} |
| 110 | + |
| 111 | + |
| 112 | +## Participants |
| 113 | + |
| 114 | +| IRC nick | Name/Nym | |
| 115 | +|-----------------|---------------------------| |
| 116 | +| wumpus | [Wladimir van der Laan][] | |
| 117 | +| sipa | [Pieter Wuille][] | |
| 118 | +| luke-jr | [Luke Dashjr][] | |
| 119 | +| gmaxwell | [Gregory Maxwell][] | |
| 120 | +| promag | [Joao Barbosa][] | |
| 121 | +| cfields | [Cory Fields][] | |
| 122 | +| achow101 | [Andrew Chow][] | |
| 123 | +| jonasschnelli | [Jonas Schnelli][] | |
| 124 | +| jnewbery | [John Newbery][] | |
| 125 | +| jimpo | [Jim Posen][] | |
| 126 | + |
| 127 | +## Disclaimer |
| 128 | + |
| 129 | +This summary was compiled without input from any of the participants in |
| 130 | +the discussion, so any errors are the fault of the summary author and |
| 131 | +not the discussion participants. In particular, quotes taken from the |
| 132 | +discussion had their capitalization, punctuation, and spelling modified |
| 133 | +to produce consistent sentences. Bracketed words and fragments, as well |
| 134 | +as background narratives and exposition, were added by the author of |
| 135 | +this summary and may have accidentally changed the meaning of some |
| 136 | +sentences. If you believe any quote was taken out of context, please |
| 137 | +[open an issue](https://github.com/bitcoin-core/bitcoincore.org/issues/new) |
| 138 | +and we will correct the mistake. |
| 139 | + |
| 140 | +[current high-priority PRs]: https://github.com/bitcoin/bitcoin/projects/8 |
| 141 | +[gitian]: https://github.com/bitcoin-core/gitian.sigs |
| 142 | +[rw conf meet notes]: /en/meetings/2018/05/24/#gui-prune-setting-and-writable-config-files |
| 143 | + |
| 144 | +{% assign log = "http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-06-07-19.00.log.html" %} |
| 145 | +[mb log]: {{log}} |
| 146 | +[log hipri]: {{log}}#l-15 |
| 147 | +[log cli args]: {{log}}#l-102 |
| 148 | + |
| 149 | +{% include link-to-issues.md issues="12196,13062,11082,12136,13111,11862" %} |
0 commit comments