Updates to release process (#11820)

Co-authored-by: Chris McFarlen <cmcfarlen@apple.com>

doc/developer-guide/release-process/index.en.rst

@@ -46,10 +46,6 @@ to the community for validation before the actual release.
 Document
 ========
 
-Gather up information about the changes for the release. The ``CHANGES`` file
-is a good starting point. You may also want to check the commits since the last
-release. The primary purpose of this is to generate a list of the important
-changes since the last release.
 
 Create or update a page on the Wiki for the release. If it is a major or minor
 release it should have its own page. Use the previous release page as a
@@ -69,11 +65,22 @@ Build
 #. Check the version in ``CMakeLists.txt``. There is a ``project`` line near the
    top with the version number.  Make sure that is correct for the release.
 
+#. Generate or update the CHANGELOG for the next release.  ::
+
+      ./tools/git/changelog.pl -o apache -r trafficserver -m X.Y.Z >
+      CHANGELOG-X.Y.Z
+
+#. Commit this file to the repository and push it to the release branch.
+
 #. Execute the following commands to make the distribution files where A is the
    next release candidate number (start with 0). ::
 
-      cmake --preset release
-      RC=A cmake --build build-release -t rel-candidate
+      RC=A cmake --preset release
+      cmake --build build-release -t rel-candidate
+
+#. Push the release tag to the repository. ::
+
+      git push <upstream repo> tag X.Y.Z-rcA
 
 These steps will create the distribution files and sign them using your key.
 Expect to be prompted twice for your passphrase unless you use an ssh key agent.
@@ -88,14 +95,22 @@ tag of the form ``X.Y.Z-rcA``.
 Distribute
 ==========
 
-The release candidate files should be uploaded to some public storage. Your
-personal storage on *people.apache.org* is a reasonable location to use.
+The release candidate files should be uploaded to apache dists. ::
+
+   svn co https://dist.apache.org/repos/dist/dev/trafficserver <local-directory>
+
+Create a directory for the next release version if necessary and then add and
+commit the release files produced above.
 
 Send the release candidate announcement to the *users* and *dev* mailing
 lists, noting that it is a release *candidate* and providing a link to the
 distribution files you uploaded. This announcement should also call for a vote
 on the candidate, generally with a 72 hours time limit.
 
+The distribution files for the release candidate will be available at::
+
+   https://dist.apache.org/repos/dist/dev/trafficserver/
+
 If the voting was successful (at least three "+1" votes and no "-1" votes),
 proceed to :ref:`release-management-official-release`. Otherwise, repeat the
 :ref:`release-management-release-candidate` process.
@@ -122,6 +137,10 @@ All three (.tar.bz2, .asc and .sha512) of the distribution files go here. If you
 then you should also remove the distribution files for the previous release.
 Allow 24 hours for the files to be distributed through the ASF infrastructure.
 
+The distribution files for the release will be available at::
+
+   https://dist.apache.org/repos/dist/release/trafficserver/
+
 The Traffic Server website must be updated. There is a git repository which you
 can access at ::