Add process step to check openstack map

During Caracal release it was discovered late that the openstack map
could use a refresh ahead of release communications. Since we should (in
theory) know the contents of the release (in terms of deliverables)
after milestone-2, add a step in the process to have a look at the map
and submit any necessary changes well ahead of the release week craze.

Change-Id: I51674b19afce0ea7b32f93ee989dbbf9df926f90

doc/source/reference/process.rst

@@ -557,6 +557,11 @@ Week after Milestone-2
 
 #. Review any remaining milestone-2 exceptions
 
+#. Now that we are past MembershipFreeze, we should check if the OpenStack map
+   will need to be updated to reflect future final release contents. If any
+   changes are needed, those should be proposed in Gerrit as changes to the
+   ``openinfra/openstack-map`` repository.
+
 #. Plan the next release cycle schedule based on the number of desired weeks or
    by making sure the cycle ends within a few weeks of the next developer
    event. Using the Monday of the close of the last cycle, and the