Merge pull request #7218 from ethereum/prepare0.511

Prepare changelog for release.

Changelog.md

@@ -1,16 +1,13 @@
-### 0.5.11 (unreleased)
+### 0.5.11 (2019-08-12)
 
 
 Language Features:
  * Inline Assembly: Support direct constants of value type in inline assembly.
 
-
-
-
 Compiler Features:
  * ABI: Additional internal type info in the field ``internalType``.
  * eWasm: Highly experimental eWasm output using ``--ewasm`` in the commandline interface or output selection of ``ewasm.wast`` in standard-json.
- * Metadata: Update the swarm hash, changes ``bzzr0`` to ``bzzr1`` and urls to use ``bzz-raw://``.
+ * Metadata: Update the swarm hash to the current specification, changes ``bzzr0`` to ``bzzr1`` and urls to use ``bzz-raw://``.
  * Standard JSON Interface: Compile only selected sources and contracts.
  * Standard JSON Interface: Provide secondary error locations (e.g. the source position of other conflicting declarations).
  * SMTChecker: Do not erase knowledge about storage pointers if another storage pointer is assigned.
@@ -18,9 +15,6 @@ Compiler Features:
  * Standard JSON Interface: Provide AST even on errors if ``--error-recovery`` commandline switch or StandardCompiler `settings.parserErrorRecovery` is true.
  * Yul Optimizer: Do not inline function if it would result in expressions being duplicated that are not cheap.
 
-
-
-
 Bugfixes:
  * ABI decoder: Ensure that decoded arrays always point to distinct memory locations.
  * Code Generator: Treat dynamically encoded but statically sized arrays and structs in calldata properly.
@@ -32,12 +26,10 @@ Bugfixes:
  * SMTChecker: Fix internal error when reporting counterexamples concerning state variables from different source files.
  * SMTChecker: Fix SMT sort mismatch when using string literals.
  * View/Pure Checker: Properly detect state variable access through base class.
- * Yul analyzer: Check availability of data objects already in analysis phase.
+ * Yul Analyzer: Check availability of data objects already in analysis phase.
  * Yul Optimizer: Fix an issue where memory-accessing code was removed even though ``msize`` was used in the program.
 
 
-
-
 ### 0.5.10 (2019-06-25)
 
 Important Bugfixes:

docs/bugs_by_version.json

@@ -746,6 +746,10 @@
         ],
         "released": "2019-06-25"
     },
+    "0.5.11": {
+        "bugs": [],
+        "released": "2019-08-12"
+    },
     "0.5.2": {
         "bugs": [
             "SignedArrayStorageCopy",