Update main README with 1.21 release news (#8619)

* Update main README with 1.21 release news

* Update README.md

Co-Authored-By: Patti Short <35278231+shortpatti@users.noreply.github.com>

* Tweak

Co-authored-by: Patti Short <35278231+shortpatti@users.noreply.github.com>

1 files changed, 9 insertions, 33 deletions

diff --git a/README.md b/README.md
index f7297bfa66..ea93bcc6d7 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 <!--
 ---
 title: "Netdata"
-date: 2020-03-31
+date: 2020-04-06
 custom_edit_url: https://github.com/netdata/netdata/edit/master/README.md
 ---
 -->
@@ -210,45 +210,21 @@ metrics, but also troubleshoot complex performance problems.
 
 ## News
 
-`Nov 27th, 2019` - **[Netdata v1.19.0 released!](https://github.com/netdata/netdata/releases)**
+`April 6, 2020` - **[Netdata v1.21.0 released!](https://github.com/netdata/netdata/releases)**
 
-Release v1.19.0 contains 2 new collectors, 19 bug fixes, 17 improvements, and 19 documentation updates.
+Release v1.21.0 contains 2 new collectors, 3 new exporting connectors, 37 bug fixes, 46 improvements, and 25 documentation updates. We also made 26 bug fixes or improvements related to the upcoming release of Netdata Cloud.
 
-We completed a major rewrite of our **web log collector** to dramatically improve its flexibility and performance. The
-[new collector](https://github.com/netdata/go.d.plugin/pull/141), written entirely in Go, can parse and chart logs from
-Nginx and Apache servers, and combines numerous improvements. Netdata now supports the LTSV log format, creates charts
-for TLS and cipher usage, and is amazingly fast. In a test using SSD storage, the collector parsed the logs for 200,000
-requests in about 200ms, using 30% of a single core.
+We added a new **collector for Apache Pulsar**, a popular open-source distributed pub-sub messaging system. We use Pulsar in our Netdata Cloud infrastructure (more on that later this month!), and are excited to start sharing metrics about our own Pulsar systems when the time comes. The Pulsar collector attempts to auto-detect any running Pulsar processes, but you can always [configure the collector](https://docs.netdata.cloud/collectors/go.d.plugin/modules/pulsar/#configuration) based on your setup.
 
-This Go-based collector also has powerful custom log parsing capabilities, which means we're one step closer to a
-generic application log parser for Netdata. We're continuing to work on this parser to support more application log
-formatting in the future.
+Also new in v1.21 is a **VerneMQ collector**. We use the open-source MQ Telemetry Transport (MQTT) broker for Netdata Cloud as well. As with Pulsar, you can [configure the VerneMQ collector](https://docs.netdata.cloud/collectors/go.d.plugin/modules/vernemq/#vernemq-monitoring-with-netdata) to auto-detect your installation in just a few steps.
 
-We have a new tutorial on [enabling the Go web log
-collector](https://docs.netdata.cloud/docs/tutorials/collect-apache-nginx-web-logs/) and using it with Nginx and/or
-Apache access logs with minimal configuration. Thanks to [Wing924](https://github.com/Wing924) for starting the Go
-rewrite!
+Our experimental exporting engine received significant updates with new connectors for **[Prometheus remote write](https://docs.netdata.cloud/exporting/prometheus/remote_write/)**, **[MongoDB](https://docs.netdata.cloud/exporting/mongodb/)**, and **[AWS Kinesis Data Streams](https://docs.netdata.cloud/exporting/aws_kinesis/)**. You can now send Netdata metrics to more than 20 additional external storage providers for long-term archiving and deeper analysis. Learn more about the [exporting engine](https://docs.netdata.cloud/exporting/) in our documentation.
 
-We introduced more **cmocka unit testing** to Netdata. In this release, we're testing how Netdata's internal web server
-processes HTTP requests—the first step to improve the quality of code throughout, reduce bugs, and make refactoring
-easier. We wanted to validate the web server's behavior but needed to build a layer of parametric testing on top of the
-CMocka test runner. Read all about our process of testing and selecting cmocka on our blog post: [Building an agile
-team's 'safety harness' with cmocka and FOSS](https://blog.netdata.cloud/posts/agile-team-cmocka-foss/).
+We upgraded our **TLS compatibility to include 1.3**, which applies to HTTPS for both Netdata's web server and streaming connections. TLS 1.3 is the most up-to-date version of the TLS protocol, and contains important fixes and improvements to ensure strong encryption. If you enabled TLS in the web server or streaming, Netdata attempts to use 1.3 by default, but you can also set the version and ciphers explicitly. Learn more in the [documentation](https://docs.netdata.cloud/web/server/#select-tls-version).
 
-Netdata's **Unbound collector** was also [completely rewritten in Go](https://github.com/netdata/go.d.plugin/pull/287)
-to improve how it collects and displays metrics. This new version can get dozens of metrics, including details on
-queries, cache, uptime, and even show per-thread metrics. See our
-[tutorial](https://docs.netdata.cloud/docs/tutorials/collect-unbound-metrics/) on enabling the new collector via
-Netdata's amazing auto-detection feature.
+The Netdata dashboard has been **completely re-written in React**. While the look and behavior hasn't changed, these under-the-hood changes enable a suite of new features, UX improvements, and design overhauls. With React, we'll be able to work faster and better resource our talented engineers.
 
-We [fixed an error](https://github.com/netdata/netdata/pull/7220) where **invalid spikes** appeared on certain charts by
-improving the incremental counter reset/wraparound detection algorithm.
-
-Netdata can now send [**health alarm notifications to IRC
-channels**](https://docs.netdata.cloud/health/notifications/irc/) thanks to [Strykar](https://github.com/Strykar)!
-
-And, Netdata can now monitor [**AM2320 sensors**](https://docs.netdata.cloud/collectors/python.d.plugin/am2320/), thanks
-to hard work from [Tom Buck](https://github.com/tommybuck).
+As part of the ongoing work to polish our **eBPF collector tech preview**, we've now proven the collector's performance is very good, and have vastly expanded the number of operating system versions the collector works on. Learn how to [enable it](https://docs.netdata.cloud/collectors/ebpf_process.plugin/) in our documentation. We've also extensively stress-tested the eBPF collector and found that it's impressively fast given the depth of metrics it collects! Read up on our benchmarking analysis [on GitHub](https://github.com/netdata/netdata/issues/8195).
 
 ---