[changelog] v1.0.0 changelog update

CHANGELOG.md

@@ -1,11 +1,41 @@
 # Changelog
 
-# 1.0.0 (PROVISIONAL - STILL WORK IN PROGRESS)
+# 1.0.0
+
+## Overview
+
+This release makes breaking changes to the APIs and configuration to provide a simpler experience both for setup and operating M3.
+
+- New [M3 website](https://m3db.io/).
+- New [M3 documentation](https://m3db.io/docs).
+- Simple [M3DB configuration](https://github.com/m3db/m3/blob/master/src/dbnode/config/m3dbnode-local-etcd.yml) and [guides](https://m3db.io/docs/quickstart/docker/).
+- M3DB [hard limits](https://m3db.io/docs/operational_guide/resource_limits/) limits for high resiliency under load.
+- Bootstrap rearchitecture, now able to boostrap hundreds of millions of recently written datapoints in minutes for reads on restart.
+- Continued focus on baseline performance release-over-release.
+
+## Features
+- **M3DB**: Namespace resolution and retention now configured dynamically via API and stored in etcd instead of being defined statically in M3Coordinator configuration.
+```
+message DatabaseCreateRequest {
+  // ...
+
+  // Optional aggregated namespace to create in 
+  // addition to unaggregated namespace
+  AggregatedNamespace aggregated_namespace = 8;
+}
+```
+- **M3DB**: Minimal configuration file with default settings looks like:
+```
+coordinator: {}
+db: {}
+```
+and includes common settings such as global query limits.
 
 ## Backwards Incompatible Changes
 
 ### Configuration
 - **M3DB**: `db.bootstrap.bootstrappers` removed
+- **M3DB**: `db.config` nested under `db.discovery.config` (`discovery` can optionally accept different `type`s of defaults instead of a custom `config`)
 - **M3Coordinator**: `cluster.namespaces.storageMetricsType` removed
 - **M3Coordinator**: `tagOptions.tagOptions` no longer supports `legacy` type
 - **M3Query**: `limits.perQuery.maxComputedDatapoints` removed
@@ -31,8 +61,15 @@ listenAddress: "..."
 - **M3Coordinator**: Removed deprecated URL `/api/v1/placement` in favor of stable preferred URL `/api/v1/services/m3db/placement`
 - **M3Coordinator**: Removed deprecated URL `/api/v1/placement/init` in favor of stable preferred URL `/api/v1/services/m3db/placement/init`
 
+### Package
+- `github.com/m3db/m3/src/x/close` removed in favor of `github.com/m3db/m3/src/x/resource`
+- `github.com/m3db/m3/src/dbnode/clock` removed in favor of `github.com/m3db/m3/src/x/clock`
+- `github.com/m3db/m3/src/x/dice/dice.go` moved to `github.com/m3db/m3/src/dbnode/storage/dice.go`
+- `github.com/m3db/m3/src/x/lockfile/lockfile.go` moved to `github.com/m3db/m3/src/dbnode/server/lockfile.go`
+
 ### Misc
 - **M3Query**: Concept of data point limit enforcers removed in favor of the other remaining query limits (e.g. max series). This also removed metrics `cost_reporter_datapoints`, `cost_reporter_datapoints_counter`, and `cost_reporter_over_datapoints_limit`.
+- Linter enabled
 
 # 0.15.17
 

site/content/operational_guide/resource_limits.md

@@ -146,18 +146,6 @@ limits:
     # If true this results in causing a query error if the query exceeds 
     # the series or blocks limit for any given individual storage node per query.
     requireExhaustive: true
-
-    # If set this limits the max number of datapoints allowed to be used by a
-    # given query. This is applied at the query service after the result has 
-    # been returned by a storage node.
-    maxFetchedDatapoints: 0
-
-  # If set will override default limits set globally.
-  global:
-    # If set this limits the max number of datapoints allowed to be used by all
-    # queries at any point in time, this is applied at the query service after 
-    # the result has been returned by a storage node.
-    maxFetchedDatapoints: 0
 ```
 
 ### Headers