Clarify release process

Improve the documentation around the release process to show the different
steps in the release schedule.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

content/policies/release-flow.md

@@ -408,11 +408,19 @@ For product releases a setup similar to
 Debian is to be used to stage updates before a new point release is done. The
 repositories used by Apertis are outlined in the following sections.
 
-Point releases are published every quarter and when this happens the staged
-updates get folded in the main repository. The last point release is a special
-case since after three months the staged updates will get folded but no
-additional point release is published. The overall support period of a product
-release is thus two years from the `.0` release.
+Every quarter a release cycle for every supported release is started with the
+goal of publishing a new point release. Before the actual point release is published
+a set of intermediate steps are performed to ensure a reliable process:
+- Soft Feature Freeze: From this point no new features are allowed to the release
+- Hard Feature Freeze / Soft Code Freeze: From this point only bug fixing is allowed,
+staged updates are folded into the main repository
+- Release Candidate / Hard Code Freeze: From this point no changes are allowed, RC
+is published for testing
+- Release: Point release is published
+
+The last point release is a special case since after three months the staged updates
+will get folded but no additional point release is published. The overall support
+period of a product release is thus two years from the `.0` release.
 
 ### Stable Repository