Language fixups (release notes and #5533) #5534

pull luke-jr wants to merge 4 commits into bitcoin:0.10 from luke-jr:010-relnotes changing 1 files +19 −16
  1. luke-jr commented at 10:20 PM on December 23, 2014: member

    Includes the language clarification in #5533

    Note this means a string change for the -help (I don't think RPC help is translated?)

  2. laanwj commented at 10:30 PM on December 23, 2014: member

    ACK

  3. laanwj added this to the milestone 0.10.0 on Dec 24, 2014
  4. fanquake commented at 1:09 AM on December 25, 2014: member

    ACK

  5. in doc/release-notes.md:None in 0cf1563269 outdated
      28 | @@ -29,7 +29,8 @@ Downgrading warning
      29 |  
      30 |  Because release 0.10.0 makes use of headers-first synchronization and parallel
      31 |  block download, the block files and databases are not backwards-compatible
      32 | -with older versions of Bitcoin Core:
      33 | +with other software (notably the Armory wallet) nor older versions of Bitcoin
    


    sipa commented at 1:10 AM on December 25, 2014:

    Did anyone actually confirm that Armory isn't compatible with this?


    luke-jr commented at 1:24 AM on December 25, 2014:

    I didn't, but I thought someone said they knew it wasn't... I guess it will be soon enough, so maybe we should leave out the parenthical region?

  6. sipa commented at 12:39 PM on December 25, 2014: member

    ACK, but please either verify that Armory is actually incompatible, or just remove that mention.

  7. fanquake commented at 1:27 PM on December 25, 2014: member

    A quick look on the forum (https://bitcointalk.org/index.php?topic=903973.0) suggests that the next Armory release will be compatible with 0.10.0

  8. sipa commented at 1:40 PM on December 25, 2014: member

    Let's leave it out then.

  9. in doc/release-notes.md:None in 0cf1563269 outdated
      41 | @@ -41,7 +42,10 @@ stored on disk, which earlier versions won't support.
      42 |  
      43 |  If you want to be able to downgrade smoothly, make a backup of your entire data
      44 |  directory. Without this your node will need start syncing (or importing from
      45 | -bootstrap.dat) anew afterwards.
      46 | +bootstrap.dat) anew afterwards. It is possible that the data from a completely
      47 | +synchronised 0.10 node may be usable in older versions as-is, but this is not
      48 | +officially supported and may break as soon as the older version attempts to
    


    Michagogo commented at 3:13 PM on December 25, 2014:

    I would drop the "officially" -- it's not unofficially supported either. Just a possibility of working.

  10. Michagogo commented at 3:15 PM on December 25, 2014: contributor

    ACK, besides that one comment

  11. luke-jr commented at 3:56 AM on December 27, 2014: member

    Changes made.

  12. luke-jr force-pushed on Dec 27, 2014
  13. laanwj commented at 4:33 AM on December 27, 2014: member

    Ugh, needs rebase

  14. en: Avoid ambiguous language regarding when transactions confirm fdad91c74f
  15. release-notes: Elaborate on downgrading warning 30340be0a4
  16. release-notes: Other minor language improvements 85bbb33760
  17. release-notes: Clarify watch-only behaviour 6915f66ca8
  18. luke-jr force-pushed on Dec 31, 2014
  19. laanwj referenced this in commit d1bcef4391 on Dec 31, 2014
  20. laanwj commented at 10:00 AM on December 31, 2014: member

    Merged via d1bcef4

  21. laanwj closed this on Dec 31, 2014

  22. reddink referenced this in commit 7b3dd82423 on May 27, 2020
  23. 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