TODO for release notes 0.15.0

[MarcoFalke]

Whenever possible, please amend the doc/release-notes.md within the pull that introduces a new fancy feature or breaks compatibility.

If this is not possible, please mention the pull here, so it can be taken care of later:

• RBF GUI (#9592, ...)
• #9602: Remove coin age priority and free transactions
• [wallet] Rescan abortability #10208 adds abortrescan RPC
• leveldb 1.20 #10138
• #9733 adds getchaintxstats RPC
• #9966 adds -persistmempool option
• #8952 adds query options to listunspent RPC
• #10478 adds bindaddr address for peer connections to getpeerinfo
• #9740 makes dumpwallet return the full absolute path to the dumped wallet
• #10400 adds uptime command

_{Feel free to edit}

The release notes are now edited on the wiki:

https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.15.0-Release-notes

[NicolasDorier]

would like #9728

[laanwj]

@NicolasDorier to be clear, this issue is to keep track of items that are already merged but need release notes updates

[laanwj]

[wallet] Rescan abortability #10208 adds abortrescan RPC

[jnewbery]

#10204 changes an RPC argument name. It's being backported to 0.14.1 - does it need 0.15 release notes as well, or do the 0.14.1 release notes cover it?

[laanwj]

[net] Allow disconnectnode RPC to be called with node id #10143 adds nodeid argument

does it need 0.15 release notes as well, or do the 0.14.1 release notes cover it?

Things should only end up in one release notes at most: the first release that has them.

[laanwj]

• #9733 adds getchaintxstats RPC
• #9966 adds -persistmempool option

[laanwj]

• #8952 adds query options to listunspent RPC

[laanwj]

• #10478 adds bindaddr address for peer connections to getpeerinfo
• #9740 makes dumpwallet return the full absolute path to the dumped wallet

[TheBlueMatt]

#10488 (and #10252) update the prioritizetransaction RPC API further after #9602, and the release notes for 9602 should include those changes as well.

[laanwj]

• #10400 adds uptime command

[TheBlueMatt]

Hopefully #10707 will make it, and will thus need release notes.

[laanwj]

Should add a release notes section about all the wonderful perf improvements in 0.15

• new and better per-utxo database format, non-atomic flushing
• tx validation caching (that's massive for performance at the tip)
• CRC instruction support in leveldb 1.20
  (and more)

[jtimon]

What about something like "more progress reducing dependencies like boost after moving to c++11"?
I remember #10502 and #10193 , but IIRC more work has done in this regard, right?

[MarcoFalke]

Boost will stick to us for a few releases at least. So this is just internal refactoring, irrelevant to release notes.

…

On Thu, Jul 13, 2017 at 10:14 PM, Jorge Timón ***@***.***> wrote: What about something like "more progress reducing dependencies like boost after moving to c++11"? I remember #10502 <#10502> and #10193 <#10193> , but IIRC more work has done in this regard, right? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9889 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGGmv3sCkjfJHv6l90R9ng8Saiy4xXjlks5sNnqIgaJpZM4MOpbC> .

[laanwj]

What about something like "more progress reducing dependencies like boost after moving to c++11"?
I remember #10502 and #10193 , but IIRC more work has done in this regard, right?

In contrast to performance improvements, which are a good selling point for a release, it doesn't seem an end-user would care about that.

After the dependency on boost completely goes away, sure, we should mention it for builders.

[TheBlueMatt]

#10784, if it makes it.

[TheBlueMatt]

#10571.

[MarcoFalke]

Due to request in yesterday's meeting, the release notes can now be edited on the wiki:

https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.15.0-Release-notes

[jnewbery]

#10604 adds listwallets command