sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-27 04:52:59 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
c39dd2ef59
dash/doc/release-notes.md

108 lines
4.0 KiB
Markdown
Raw Normal View History

doc: Empty release notes for next release Now that 0.9 is branched off, the new release notes for 0.10 or 0.11 or 1.0 should be added here. Edits to preliminary 0.9.0 release notes should be made in the 0.9.0 branch.
2014-03-03 09:41:18 +01:00
(note: this is a temporary file, to be added-to by anybody, and moved to
release-notes at release time)
estimatefee / estimatepriority RPC methods New RPC methods: return an estimate of the fee (or priority) a transaction needs to be likely to confirm in a given number of blocks. Mike Hearn created the first version of this method for estimating fees. It works as follows: For transactions that took 1 to N (I picked N=25) blocks to confirm, keep N buckets with at most 100 entries in each recording the fees-per-kilobyte paid by those transactions. (separate buckets are kept for transactions that confirmed because they are high-priority) The buckets are filled as blocks are found, and are saved/restored in a new fee_estiamtes.dat file in the data directory. A few variations on Mike's initial scheme: To estimate the fee needed for a transaction to confirm in X buckets, all of the samples in all of the buckets are used and a median of all of the data is used to make the estimate. For example, imagine 25 buckets each containing the full 100 entries. Those 2,500 samples are sorted, and the estimate of the fee needed to confirm in the very next block is the 50'th-highest-fee-entry in that sorted list; the estimate of the fee needed to confirm in the next two blocks is the 150'th-highest-fee-entry, etc. That algorithm has the nice property that estimates of how much fee you need to pay to get confirmed in block N will always be greater than or equal to the estimate for block N+1. It would clearly be wrong to say "pay 11 uBTC and you'll get confirmed in 3 blocks, but pay 12 uBTC and it will take LONGER". A single block will not contribute more than 10 entries to any one bucket, so a single miner and a large block cannot overwhelm the estimates.
2014-03-17 13:19:54 +01:00
build: bump version to 0.15.99 Now that 0.15 branch has been split off, master is 0.15.99 (pre-0.16). Also clean out release notes. Tree-SHA512: 160f712fae7bfc51e49e36a27ab01f5c243b79a19a70312df95f9bc5cb8067c70aa88911f741fd1625bee549a70655eaea24d98f6049d98c3c14ee1b3143f4cb
2017-02-17 17:26:01 +01:00
Bitcoin Core version *version* is now available from:
doc: Update release process The actual release process quite diverged from what was written here, also clarify things a bit.
2016-04-15 13:21:16 +02:00
build: Bump version to 0.16.99 Also clean out release notes. Tree-SHA512: c4d5b52c089e14438be37381e1b0dab3711cc72aa8d345d1024169fff0055f3d021c8ca9d46fb794110694ebcbf7cbca0a12619f650873c9d381530adea7100e
2018-01-30 13:49:15 +01:00
<https://bitcoincore.org/bin/bitcoin-core-*version*/>
doc: Update release process The actual release process quite diverged from what was written here, also clarify things a bit.
2016-04-15 13:21:16 +02:00
This is a new major version release, including new features, various bugfixes
and performance improvements, as well as updated translations.
doc: Update release notes for 0.16.0
2017-09-12 10:04:27 +02:00
Please report bugs using the issue tracker at GitHub:
doc: Update release process The actual release process quite diverged from what was written here, also clarify things a bit.
2016-04-15 13:21:16 +02:00
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
doc: Update release notes from wiki Update release notes from wiki, and fill in authors list from git. Additional credits: - Awemany (for #10854) - Gregory Maxwell (release notes writing) - John Newbery (release notes writing) - Kibbled Jive Elk Zoo (for https://github.com/bitcoin/bitcoin/pull/10177#issuecomment-309244097) - Luke Dashjr (release notes writing) - Marco Falke (release notes writing) - Pieter Wuille (release notes writing) - Rusty Russell (release notes writing) - tintinweb (for early-announcing miniupnp CVE-2017-8798, forgot this for 0.14.2) Tree-SHA512: 8024eb761fcac4bb7f16ba3a9db376508f1f1bcf8a89cfb5e2928ad384675d3e912cada6ffef7d5aac181a965ebb8b823f6a63d9e976c1be753ec8eb9a8b9ef5
2017-08-14 16:45:58 +02:00
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has completely
Add release notes for -walletdir and wallets/ dir
2017-10-09 10:45:01 +02:00
shut down (which might take a few minutes for older versions), then run the
doc: Update release notes for 0.16.0
2017-09-12 10:04:27 +02:00
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on Mac)
doc: Update release notes from wiki Update release notes from wiki, and fill in authors list from git. Additional credits: - Awemany (for #10854) - Gregory Maxwell (release notes writing) - John Newbery (release notes writing) - Kibbled Jive Elk Zoo (for https://github.com/bitcoin/bitcoin/pull/10177#issuecomment-309244097) - Luke Dashjr (release notes writing) - Marco Falke (release notes writing) - Pieter Wuille (release notes writing) - Rusty Russell (release notes writing) - tintinweb (for early-announcing miniupnp CVE-2017-8798, forgot this for 0.14.2) Tree-SHA512: 8024eb761fcac4bb7f16ba3a9db376508f1f1bcf8a89cfb5e2928ad384675d3e912cada6ffef7d5aac181a965ebb8b823f6a63d9e976c1be753ec8eb9a8b9ef5
2017-08-14 16:45:58 +02:00
or `bitcoind`/`bitcoin-qt` (on Linux).
The first time you run version 0.15.0, your chainstate database will be converted to a
new format, which will take anywhere from a few minutes to half an hour,
depending on the speed of your machine.
Note that the block database format also changed in version 0.8.0 and there is no
automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
directly from 0.7.x and earlier without redownloading the blockchain is not supported.
However, as usual, old wallet versions are still supported.
Downgrading warning
-------------------
The chainstate database for this release is not compatible with previous
releases, so if you run 0.15 and then decide to switch back to any
older version, you will need to run the old release with the `-reindex-chainstate`
option to rebuild the chainstate data structures in the old format.
If your node has pruning enabled, this will entail re-downloading and
processing the entire blockchain.
doc: Mention Windows XP end of support in release notes Closes #7681.
2016-06-22 16:29:00 +02:00
Compatibility
==============
Trim down the XP notice and say more about what we support. The big notice at the top of the release note is not interesting to most users now and apparently comes across poorly to some. Better to provide more information about what we do support.
2017-01-14 02:21:41 +01:00
Bitcoin Core is extensively tested on multiple operating systems using
[docs] Minor improvements to Compatibility Notes Progressed from Windows Vista to Windows 7 for OS testing statement.
2018-02-26 22:52:25 +01:00
the Linux kernel, macOS 10.8+, and Windows 7 and newer (Windows XP is not supported).
Trim down the XP notice and say more about what we support. The big notice at the top of the release note is not interesting to most users now and apparently comes across poorly to some. Better to provide more information about what we do support.
2017-01-14 02:21:41 +01:00
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
doc: Mention Windows XP end of support in release notes Closes #7681.
2016-06-22 16:29:00 +02:00
Autoprune release notes included
2015-05-26 21:32:25 +02:00
Notable changes
===============
rpc: Reject deprecated reserveChangeKey in fundrawtransaction
2018-02-11 04:12:43 +01:00
RPC changes
------------
### Low-level changes
[rpc] createrawtransaction: Accept sorted outputs
2017-12-11 21:24:02 +01:00
- The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client.
- The `fundrawtransaction` RPC will reject the previously deprecated `reserveChangeKey` option.
rpc: Reject deprecated reserveChangeKey in fundrawtransaction
2018-02-11 04:12:43 +01:00
Allow wallet files not in -walletdir directory Remove restriction that -wallet filenames can only refer to files in the -walletdir directory.
2017-11-14 19:32:41 +01:00
External wallet files
---------------------
The `-wallet=<path>` option now accepts full paths instead of requiring wallets
Create new wallet databases as directories rather than files This change should make it easier for users to make complete backups of wallets because they can now just back up the specified `-wallet=<path>` path directly, instead of having to back up the specified path as well as the transaction log directory (for incompletely flushed wallets). Another advantage of this change is that if two wallets are located in the same directory, they will now use their own BerkeleyDB environments instead using a shared environment. Using a shared environment makes it difficult to manage and back up wallets separately because transaction log files will contain a mix of data from all wallets in the environment.
2017-11-15 21:44:36 +01:00
to be located in the -walletdir directory.
Newly created wallet format
---------------------------
If `-wallet=<path>` is specified with a path that does not exist, it will now
create a wallet directory at the specified location (containing a wallet.dat
data file, a db.log file, and database/log.?????????? files) instead of just
creating a data file at the path and storing log files in the parent
directory. This should make backing up wallets more straightforward than
before because the specified wallet path can just be directly archived without
having to look in the parent directory for transaction log files.
For backwards compatibility, wallet paths that are names of existing data files
in the `-walletdir` directory will continue to be accepted and interpreted the
same as before.
Low-level RPC changes
---------------------
- When bitcoin is not started with any `-wallet=<path>` options, the name of
the default wallet returned by `getwalletinfo` and `listwallets` RPCs is
now the empty string `""` instead of `"wallet.dat"`. If bitcoin is started
with any `-wallet=<path>` options, there is no change in behavior, and the
name of any wallet is just its `<path>` string.
Allow wallet files not in -walletdir directory Remove restriction that -wallet filenames can only refer to files in the -walletdir directory.
2017-11-14 19:32:41 +01:00
Format timestamps using ISO 8601 formatting (e.g. "2018-02-28T12:34:56Z") * Z is the zone designator for the zero UTC offset. * T is the delimiter used to separate date and time. This makes it clear for the end-user that the date/time logged is specified in UTC and not in the local time zone.
2018-02-28 16:46:31 +01:00
### Logging
- The log timestamp format is now ISO 8601 (e.g. "2018-02-28T12:34:56Z").
doc: Clean out release notes Now that 0.13 has branched, release notes for 0.13 should be maintained there, and the release notes file on master is for 0.14 release notes.
2016-07-18 14:00:05 +02:00
Credits
=======
Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Reference in New Issue Copy Permalink