20.10.0 changelog (#1527)

* Remove ROADMAP.md and link Wiki Roadmap in README.md

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Update changelog to add EIP 2315

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Update Changelog for 1.5

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Remove developper advocate contact

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Update changelog to bring into line with release notes

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Remove known issue

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>
pull/1531/head
Tim Beiko 4 years ago committed by GitHub
parent ea2e9e253c
commit f3abf47977
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 38
      CHANGELOG.md
  2. 11
      KNOWN_ISSUES.md

@ -22,11 +22,17 @@ Deprecated in 1.5.1
- CLI option `--privacy-precompiled-address` option removed. This address is now derived, based
on `--privacy-onchain-groups-enabled`. [\#1222](https://github.com/hyperledger/besu/pull/1222)
## 20.10.0
## Release format
Hyperledger Besu is moving its versioning scheme to [CalVer](https://calver.org/) starting with the 20.10.0 (formerly 1.6.0) release. More information about the specific version of CalVer Besu is using can be found on the [wiki](https://wiki.hyperledger.org/display/BESU/Using+CalVer+for+Besu+Releases).
## 20.10 Breaking Changes
When upgrading to 20.10, ensure you've taken into account the following breaking changes.
### JSON-RPC HTTP Error Codes For Valid Calls
### JSON-RPC HTTP Error Codes For Valid Calls ([\#1426](https://github.com/hyperledger/besu/pull/1426))
Prior versions of Besu would set the HTTP Status 400 Bad Request for JSON-RPC requests that completed in an error, regardless of the kind of error. These responses could include a complete JSON-RPC response with an error field.
@ -34,27 +40,18 @@ In Besu version 20.10, properly formatted requests that have valid parameters (c
Users of Web3J should note that many calls will now return a result with the error field containing the message whereas before a call would throw an exception with the error message as the exception message.
## 20.10.0-RC2
## 20.10.0 Additions and Improvements
### Additions and Improvements
* Added support for ECIP-1099: Calibrate Epoch Duration. [\#1421](https://github.com/hyperledger/besu/pull/1421)
* Added support for ECIP-1099 / Classic Thanos Fork: Calibrate Epoch Duration. [\#1421](https://github.com/hyperledger/besu/pull/1421) [\#1441](https://github.com/hyperledger/besu/pull/1441) [\#1462](https://github.com/hyperledger/besu/pull/1462)
* Added the Open Telemetry Java agent to report traces to a remote backend. Added an example to showcase the trace reporting capabilities.
* Rename genesis config option ecip1099Block to thanosBlock. [\#1462](https://github.com/hyperledger/besu/pull/1462)
## 20.10.0-RC1
### Release format
Hyperledger Besu is moving its versioning scheme to [CalVer](https://calver.org/) starting with the 20.10.0 (f.k.a. 1.6.0) release. More information about the specific version of CalVer Besu is using can be found on the [wiki](https://wiki.hyperledger.org/display/BESU/Proposal+-+CalVer+for+Besu+Releases).
### Additions and Improvements
* Added EvmTool binary to the distribution. EvmTool is a CLI that can execute EVM bytecode and execute ethereum state tests. Documentation for it is available [here](https://besu.hyperledger.org/en/stable/HowTo/Troubleshoot/Use-EVM-Tool/). [\#1465](https://github.com/hyperledger/besu/pull/1465)
* Added support for the upcoming YOLOv2 ephemeral testnet and removed the flag for the deprecated YOLOv1 ephemeral testnet. [#1386](https://github.com/hyperledger/besu/pull/1386)
* Added `debug_standardTraceBlockToFile` JSON-RPC API. This API accepts a block hash and will replay the block. It returns a list of files containing the result of the trace (one file per transaction). [\#1392](https://github.com/hyperledger/besu/pull/1392)
* Added `debug_standardTraceBadBlockToFile` JSON-RPC API. This API is similar to `debug_standardTraceBlockToFile`, but can be used to obtain info about a block which has been rejected as invalid. [\#1403](https://github.com/hyperledger/besu/pull/1403)
* Added support for EIP-2929 to YOLOv2. [#1387](https://github.com/hyperledger/besu/pull/1387)
* Added `--start-block` and `--end-block` to the `blocks import` subcommand [\#1399](https://github.com/hyperledger/besu/pull/1399)
* Added support for multi-tenancy when using the early access feature of [onchain privacy group management](https://besu.hyperledger.org/en/stable/Concepts/Privacy/Onchain-PrivacyGroups/)
* Added `--privacy-flexible-groups-enabled` as an alternative for `--privacy-onchain-groups-enabled` CLI option
* \[Reverted\] Fixed memory leak in eth/65 subprotocol behavior. It is now enabled by default. [\#1420](https://github.com/hyperledger/besu/pull/1420), [#1348](https://github.com/hyperledger/besu/pull/1348), [#1321](https://github.com/hyperledger/besu/pull/1321)
### Bug Fixes
@ -66,13 +63,18 @@ Hyperledger Besu is moving its versioning scheme to [CalVer](https://calver.org/
- [Eth/65 loses peers](KNOWN_ISSUES.md#eth65-loses-peers)
- [Fast sync when running Besu on cloud providers](KNOWN_ISSUES.md#fast-sync-when-running-besu-on-cloud-providers)
- [Privacy users with private transactions created using v1.3.4 or earlier](KNOWN_ISSUES.md#privacy-users-with-private-transactions-created-using-v134-or-earlier)
- [Changes not saved to database correctly causing inconsistent private states](KNOWN_ISSUES.md#Changes-not-saved-to-database-correctly-causing-inconsistent-private-states)
## Deprecated and Scheduled for removal in _Next_ Release
### --privacy-precompiled-address
Deprecated in 1.5.1
- CLI option `--privacy-precompiled-address` option removed. This address is now derived, based
on `--privacy-onchain-groups-enabled`. [\#1222](https://github.com/hyperledger/besu/pull/1222)
### Download link
### Download link
https://dl.bintray.com/hyperledger-org/besu-repo/besu-20.10.0.zip
https://dl.bintray.com/hyperledger-org/besu-repo/besu-20.10.0-RC1.zip
sha256sum: `ae8979e43a81a69d3dcf207b556275d94edbb67490747f0454269f87d38ee4fb`
sha256sum: `2b50a375aae64b838a2cd9d43747006492cae573f1be11745b7f643646fd5a01`
## 1.5.5

@ -38,14 +38,3 @@ A critical issue for privacy users with private transactions created using Hyper
or earlier has been identified. If you have a network with private transaction created using v1.3.4
or earlier, please read the following and take the appropriate steps:
https://wiki.hyperledger.org/display/BESU/Critical+Issue+for+Privacy+Users
## Changes not saved to database correctly causing inconsistent private states
While running reorg testing on Besu and Orion, inconsistent private states were observed in some long running tests
when state changes were not saved to the database correctly when executing the private transaction.
Workaround -> As the private transaction payloads have all been distributed and the privacy marker
transactions included in the chain, resynchronizing the node with an inconsistent state will re-execute
the private transactions.
A fix for this issue is being actively worked on.

Loading…
Cancel
Save