Squashes DTR beta release notes for GA

_data/toc.yaml

@@ -1041,6 +1041,8 @@ toc:
           section:
           - path: /datacenter/dtr/2.2/guides/admin/upgrade/release-notes/
             title: Release notes
+          - path: /datacenter/dtr/2.2/guides/admin/upgrade/incompatibilities-and-breaking-changes/
+            title: Incompatibilities and breaking changes
           - path: /datacenter/dtr/2.2/guides/admin/upgrade/
             title: Upgrade
       - sectiontitle: Configure

datacenter/dtr/2.2/guides/admin/upgrade/incompatibilities-and-breaking-changes.md

@@ -0,0 +1,9 @@
+---
+title: Incompatibilities and breaking changes
+description: Learn about the incompatibilities and breaking changes introduced by Docker Trusted Registry version {{ page.dtr_version }}
+keywords: docker, ucp, upgrade, incompatibilities
+---
+
+With Docker Trusted Registry {{ page.dtr_version }}, the `/load_balancer_status`
+endpoint is deprecated and is going to be removed in future versions. Use the
+`/health` endpoint instead.

datacenter/dtr/2.2/guides/admin/upgrade/release-notes.md

@@ -10,54 +10,9 @@ known issues for each DTR version.
 You can then use [the upgrade instructions](index.md),
 to upgrade your installation to the latest release.
 
-## DTR 2.2.0 beta 2
+## DTR 2.2.0
 
-(25 Jan 2017)
+(9 Feb 2017)
-
-* Security scans
-  * After scanning an empty images, DTR now tells that the image is empty instead
-  of leaving the UI empty
-  * The UI now shows that an image was not scanned instead of saying it is empty
-  * When you disable automatic security updates, DTR no longer continues searching
-  for updates online
-
-* UI
-  * On the repositories list you can now click anywhere on the row to see the
-  repository details
-  * When you don't have permissions to see the repository details, the UI now
-  shows that you don't have permissions instead of saying it has no manifests
-
-* API
-  * The `docker/search` command was relaxed to return more results
-  * Webhooks on a manifest push now include data about the operating system and architecture
-  * Webhooks on a manifest delete now includes a unique id instead of a username
-  * Webhooks on a tag deletion now include data about the author
-  * Adding a duplicate webhook now returns HTTP 400 errors instead of 500
-  * Updating a repository now triggers a Webhooks
-  * Jobs are retried if the worker running them stops unexpectedly
-  * When a job runner worker reached its capacity it would stop accepting job
-  even after executing all the jobs allocated. This has been fixed
-  * The `imagescan/status` endpoint is now restricted to admin users
-  * Using the `imagescan/status` endpoint while the vulnerability database is
-  updating now returns HTTP 403 errors instead of 500
-
-* docker/dtr image
-  * The `docker/dtr install` command now shows all the nodes that are part of a
-  UCP cluster for you choose on which node to deploy DTR
-  * The install command was improved to avoid deploying DTR to a node where it
-  cannot run due to port collisions
-  * The `docker/dtr install --ucp-node` flag is now mandatory
-  * The install command no longer allows deploying replicas with duplica ids
-  * The upgrade command now validates if all tags were migrated to the latest
-  version before trying to migrate blob links
-
-
-
-
-
-## DTR 2.2.0 beta 1
-
-(10 Jan 2017)
 
 **New features**
 
@@ -69,16 +24,26 @@ events like image push, repository creation, and others
 
 **General improvements**
 
-* Improved error messages to be more meaningful and help troubleshoot the problem
+* UI/UX
-* Several UI/UX improvements to the DTR configuration page and user settings page
+  * Improved error messages to be more meaningful and help troubleshoot the problem
-* Several UI/UX improvements to the user settings page
+  * Several UI/UX improvements to the DTR configuration page and user settings page
-* Several improvements to the search bar used in the UI
+  * Several improvements to the search bar used in the UI
+
+* docker/dtr image
+  * The `docker/dtr install` command now shows all the nodes that are part of a
+  UCP cluster for you choose on which node to deploy DTR
+  * The install command was improved to avoid deploying DTR to a node where it
+  cannot run due to port collisions
+  * The `docker/dtr install --ucp-node` flag is now mandatory
+  * The install command no longer allows deploying replicas with duplica ids
+  * The upgrade command now validates if all tags were migrated to the latest
+  version before trying to migrate blob links
 
 **Bugs fixed**
 
 * When creating a repository, the length of the repository now is consistent
 between the UI and API
-* The UI now validate and doesn't allow create repository names using uppercase
+* The UI now validate and doesn't allow creating repository names with uppercase
 letters
 * You can now create organizations with dashes in the name
 * Fixed a bug that didn't allow deleting users immediately after they were
@@ -89,18 +54,11 @@ created
 * Organization administrators can now see the repositories owned by the organization
 * The garbage collection settings now show the correct cron values
 * You can now specify DTR to use port 443 when installing DTR
+* When you don't have permissions to see the repository details, the UI now
+shows that you don't have permissions instead of saying it has no manifests
+* Jobs are retried if the worker running them stops unexpectedly
 
 **Deprecation**
 
 The `/load_balancer_status` is deprecated and is going to be removed in future
 versions. Use the `/health` endpoint instead.
-
-**Known issues**
-
-* When viewing the result of a security scan, clicking on a layer sometimes
-highlights two different layers
-* The `docker search` command is not returning exact matches to the user namespace
-* The UI becomes slow when synchronizing more than 400k LDAP users
-* The flag `docker/dtr reconfigure --tls-syslog-certs` may break the connection
-to syslog since not all replicas have the correct TLS certificates locally
-* The `docker/dtr remove` sometimes doesn't remove all the DTR volumes