Add reference to preparing next major release doc; reference automate…

…d workflow from freeze docs (#422)

* Add reference to preparing next major release doc.

* Reference automated workflow from freeze docs.

* Reformulate.

docs/automated-process.md

@@ -149,3 +149,7 @@ next to the release version:
 
 2. Set `existing-branch` to the branch you pushed to the `ansible-build-data`
    repository.
+
+When the new major release has been done, remember to prepare the directory for
+the next major Ansible release. How to do this is described in [Setting up for a
+new major release](new-ansible-and-freezes.md#setting-up-for-a-new-major-release).

docs/new-ansible-and-freezes.md

@@ -95,6 +95,12 @@ TODO: Improve the release playbook to support this case without requiring extra
 Beyond the regular [Ansible Release Process](release-process.md), X.Y.0
 releases require special handling before running the release playbook.
 
+!!! note
+    This can be done in a simpler fashion when using the [automated release
+    process](automated-process.md). See the regular automated workflow for
+    versions up to rc1, and the [Special builds](automated-process.md#special-builds)
+    section for further release candidates and for the final major release.
+
 1. Determine the previous and the current releases
 
     ``` sh