doc/release-notes: Various cleanups #9790

pull luke-jr wants to merge 1 commits into bitcoin:0.14 from luke-jr:0.14-relnotes changing 1 files +28 −42
  1. luke-jr commented at 10:40 PM on February 17, 2017: member
    • Remove minor/obvious changes
    • Clarify and document new options in "Minimum Fee Rate Policies"
    • Attribution fixes
    • Remove deprecation of miner priority sorting
  2. doc/release-notes: Various cleanups
    - Remove minor/obvious changes
    - Clarify and document new options in "Minimum Fee Rate Policies"
    - Attribution fixes
    - Remove deprecation of miner priority sorting
    f98c853c58
  3. jnewbery commented at 11:32 PM on February 17, 2017: member

    NACK. You seem to have accidentally removed the part about priority transaction sorting for mining being deprecated in Core and being removed in the next major version.

  4. luke-jr commented at 11:35 PM on February 17, 2017: member

    Not accidentally, it's documented in the summary. There is no consensus to remove priority mining.

  5. sipa commented at 11:42 PM on February 17, 2017: member

    Please stop this, @luke-jr. I'm aware you dislike the removal of priority mining and respect that, but it seems the vast majority of contributors to the project agree it is pointless to maintain at this point.

  6. luke-jr commented at 11:53 PM on February 17, 2017: member

    @sipa I tried to find a compromise where nobody had to maintain it besides me, but certain people were stubborn and refused. So the status quo of "no consensus to remove" remains for now.

  7. sipa commented at 11:56 PM on February 17, 2017: member

    @luke-jr This is not a consensus change, and it's not up to you to block this. I absolutely respect that you want priority mining to remain available, but you'll have to do it in your own fork, or develop an external tool that implements it through prioritizetransaction RPC calls (which seems very useful in any case as an example).

  8. luke-jr commented at 12:07 AM on February 18, 2017: member

    @sipa I think this comment deserves proper consideration before any final decision is made. But in the case that priority is to be removed, how about simply adding to the current text, "Miners who wish to retain this feature should switch to Bitcoin Knots, where it will continue to be maintained and supported for the time being."?

  9. sipa commented at 12:27 AM on February 18, 2017: member

    @luke-jr Ok, I've commented.

    how about simply adding to the current text, "Miners who wish to retain this feature should switch to Bitcoin Knots, where it will continue to be maintained and supported for the time being."?

    I disagree with recommending the use of software based on a feature we don't consider relevant ourselves.

  10. luke-jr commented at 12:51 AM on February 18, 2017: member

    I do consider it relevant, and even aside from that, it is up to miners to decide on their own if they consider it relevant, not to have information about its availability suppressed so they are forced out of using it.

  11. sipa commented at 1:16 AM on February 18, 2017: member

    I do consider it relevant

    That's fine, you can recommend whatever you like. But you can't decide alone what goes into Bitcoin Core's release notes.

  12. fanquake added the label Docs and Output on Feb 19, 2017
  13. MarcoFalke commented at 11:58 AM on March 8, 2017: member

    Closing. This missed the deadline.

  14. MarcoFalke closed this on Mar 8, 2017

  15. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-14 15:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me