Remove refs/for/ deprecation
refs/for/-deprecation was reverted.
Change-Id: I4c65443182a90d414d13e3a26ef5e2b5f55e67d8
diff --git a/pages/site/releases/2.16.md b/pages/site/releases/2.16.md
index 1d8f780..db0b1fc 100644
--- a/pages/site/releases/2.16.md
+++ b/pages/site/releases/2.16.md
@@ -139,54 +139,6 @@
easily. Detailed information about request tracing can be found in the
[request tracing documentation](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/user-request-tracing.html).
-## ACL Changes
-
-### ACLs: refs/for/ namespace is now deprecated
-
-The `refs/for` namespace is no longer used when evaluating access rights.
-
-#### Background
-Removing the `refs/for` support in the ACLs intends to solve the following
-issues:
-
-* Vast majority of permissions are defined on "real" branches. Forcing users to
-define a small subset of the permissions on `refs/for/*` hinders readability and
-the understanding of the applied ACLs.
-
-* For people using `refs/publish/` to upload reviews, it is confusing to force
-Project Owners to set the push rules on `refs/for/` to allow creation of
-changes.
-
-* Having `refs/for/` in the ACL UI makes it impossible to look at one single
-ACL section and acknowledge with certainty which rules will be in effect for
-that ref.
-
-#### Changes
-
-* Instead of defining push on `refs/for/*` a new `Create Review` permission is
-introduced. Like other permissions, it should be defined on `refs/heads/*` (or
-`refs/*`).
-
-* A new `Submit on Push` option for the `Submit` permission, which will enable
-the %submit push parameter and remove the need to specify `Submit` on
-`refs/for/*`.
-
-* `Add Patch Set` will work the same way, but should be specified on
-`refs/heads/*` (just like the new `Create Review` permission).
-
-* `Push Merges` will work the same way, but should be specified on
-`refs/heads/*` instead of `refs/for/*`.
-
-
-#### Migration
-
-Any permission that could previously be applied to `refs/for` will
-automatically be migrated to the new permission upon loading the ACLs.
-
-Note: The configuration is not automatically resaved, so the next time the
-user edits the ACLs from the UI, the migrated ACLs will be shown and possibly
-saved if the user chose to do so.
-
## Dependency Updates
* Update args4j to 2.33
