diff --git a/RELEASE_GUIDE.md b/RELEASE_GUIDE.md
index d46911b0ce..68f713bfda 100644
--- a/RELEASE_GUIDE.md
+++ b/RELEASE_GUIDE.md
@@ -14,6 +14,11 @@ All releases will be made by creating a PR which bumps the version field in the
 1. If you are making a minor or major release (or prereleases of one) make sure you are on the `master` branch.
 1. If you are making a patch release (or a prerelease for one) make sure you are on the `release/v<MAJOR>.<MINOR>` branch.
 1. Run `npm run create-release-pr`.
+    - NOTES:
+        - The PRs that picked are based on which milestone they are marked as being a part of and if they have already been released
+        - The milestone is automatically computed from the version of the `@k8slens/core`.
+        If there is are any prerelease tags then the milestone will be for the next stable version (no prereleases).
+        Otherwise, it will be for the next patch version.
 1. Pick the PRs that you want to include in this release using the keys listed.
     - If you are making a patch release this might include fixing up some cherry-picking of commits. These actions should be done in a separate terminal.
     - If a package version is having a major version bump then `npm` will complain about `peerDependency` conflicts. These will have to be fixed up separately.