Update the release process

docs/product/release.rst

@@ -85,13 +85,18 @@ Some functions of the **release manager** are:
   to make sure no regressions were introduced on the tests executed post-merge.
 * Creating high priority tickets in case the tests are failing on master.
 * Coordinating story tickets for the milestone.
-* After sending the release branch to RQM, check that the Downloads page is updated.
-* Check that a tag is created for the release, and that the tag points to the release branch and   not the release merge.
+* After sending the release branch to RQM, check that the Downloads page is updated
+  and that the trial download links (only direct links) are updated.
+* When creating the release PR add the release news, staging links, direct links to
+  the trial versions, description of what the review and the reviewer names.
+* Check that a tag is created for the release, and that the tag points to the
+  release branch and not the release merge.
 * Check that RQM has closed the release PR and associated Trac.
 * After the Downloads page is updated, ensure that the release branch is merged
   with the master branch.
 * Sends the newsletter to the relevant list/s and updates associated customers
   that are waiting for the release.
+* Update the website with the release news.
 
 Release Manager should look into obtaining access to the following: