diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 4c9c2d1be..c1d69e7fb 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,7 +1,62 @@
 # Community Solid Server release notes
 
+## v2.0.0
+### New features
+- Pod owners always have Control access to resources stored in their Pod.
+- The server now offers a one-time setup upon first boot.
+  This can be accessed by going to `/setup`.
+  Configurations with a persistent backend enforce setup before the server can be used,
+  preventing unintended modifications in the backend.
+  These have corresponding `*-no-setup.json` files where setup is disabled,
+  so the pre-v2.0 behavior is still available.
+- `ETag`, `Last-Modified`, `If-None-Match`, and related conditional headers are supported.
+- `PATCH`ing containers is now supported.
+- `PUT`/`POST` requests with empty bodies are supported.
+- WebACL authorization supports groups.
+- IDP components (registration, login, etc.) fully support JSON input and output.
+- There is a new configuration `sparql-file-storage.json` to have a SPARQL backend with file storage.
+  `sparql-file-storage.json`.
+- A server can be set up to restrict access to IDP components using WebACL.
+  A consequence of this is that IDP components are only accessible using a trailing slash.
+  E.g., `/idp/register/` works, `/idp/register` will error.
+
+### Configuration changes
+You might need to make changes to your v1 configuration if you use a custom config.
+
+The following changes pertain to the imports in the default configs:
+- There are 2 new configuration options that for which a valid option needs to be imported:
+  - `/app/setup` determines how and if setup should be enabled.
+  - `/identity/access` determines if IDP access (e.g., registration) should be restricted
+- The `/app/init/default.json` configuration no longer initializes the root container. 
+  This behaviour has been moved to the other options for `/app/init`.
+- `/ldp/permissions` changed to `/ldp/modes` and only has a default option now.
+
+The following changes are relevant for v1 custom configs that replaced certain features.
+The path indicates which JSON-LD files were impacted by the change.
+- `IdentityProviderHttpHandler` and `InteractionRoute` arguments have changed substantially. 
+  - `/identity/handler/default.json`
+  - `/identity/handler/interaction/*`
+  - `/identity/registration/*`.
+- All internal storage is now stored in the `/.internal/` container. 
+  - `/storage/key-value/resource-store.json`. 
+- Patching related classes have changed. 
+  - `/storage/middleware/stores/patching.json`.
+- `BasicRequestParser` now needs a `conditionsParser` argument.
+  - `/ldp/handler/components/request-parser.json`.
+- `LinkTypeParser` has been renamed to `LinkRelParser` and now takes mappings as input. 
+  - `/ldp/metadata-parser/*`
+- `ComposedAuxiliaryStrategy` `isRootRequired` has been renamed to `requiredInRoot`. 
+  - `/util/auxiliary/strategies/acl.json`.
+- Many changes to authentication and authorization structure. 
+  - Config `/ldp/authentication/*` and `/ldp/authorization/*`.
+- All `HttpHandler`s have been changed. 
+  - `/app/setup/handlers/setup.json`
+  - `/http/handler/default.json`
+  - `/identity/handler/default.json`
+  - `/ldp/handler/default.json`.
+
 ## v1.1.0
-New features:
+### New features
 - The `ConstantConverter` can now filter on media type using the `enabledMediaRanges` and `disabledMediaRanges` options. That way, the server can be configured to bypass a default UI when accessing images or PDF documents. (https://github.com/solid/community-server/discussions/895, https://github.com/solid/community-server/pull/925)
 
 ## v1.0.0