Update release plan (microsoft#23431)

.github/release_plan.md

@@ -11,7 +11,7 @@ Feature freeze is Monday @ 17:00 America/Vancouver, XXX XX. At that point, commi
 ✅ | ~~January~~   | ~~Eleanor~~   | ~~Karthik~~     |
 ✅ | ~~February~~  | ~~Kartik~~    | ~~Anthony~~     |
 ✅| ~~March~~     | ~~Karthik~~   | ~~Eleanor~~     |
-| April     | Paula     | Eleanor      |
+✅| ~~April~~     | ~~Paula~~     | ~~Eleanor~~      |
 | May       | Anthony   | Karthik     |
 | June      | Eleanor   | Paula       |
 | July      | Anthony   | Karthik     |
@@ -36,13 +36,12 @@ NOTE: the number of this release is in the issue title and can be substituted in
 
 
 ### Step 1:
-##### Bump the version of `main` to be a release candidate (also updating debugpy dependences, third party notices, and package-lock.json).❄️ (steps with ❄️ will dictate this step happens while main is frozen 🥶)
+##### Bump the version of `main` to be a release candidate (also updating third party notices, and package-lock.json).❄️ (steps with ❄️ will dictate this step happens while main is frozen 🥶)
 
 -   [ ] checkout to `main` on your local machine and run `git fetch` to ensure your local is up to date with the remote repo.
 -   [ ] Create a new branch called  **`bump-release-[YYYY.minor]`**.
 -   [ ] Change the version in `package.json` to the next **even** number and switch the `-dev` to `-rc`. (🤖)
 -   [ ] Run `npm install` to make sure `package-lock.json` is up-to-date _(you should now see changes to the `package.json` and `package-lock.json` at this point which update the version number **only**)_. (🤖)
--   [ ] Check [debugpy on PyPI](https://pypi.org/project/debugpy/) for a new release and update the version of debugpy in [`install_debugpy.py`](https://github.com/microsoft/vscode-python/blob/main/python_files/install_debugpy.py) if necessary.
 -   [ ] Update `ThirdPartyNotices-Repository.txt` as appropriate. You can check by looking at the [commit history](https://github.com/microsoft/vscode-python/commits/main) and scrolling through to see if there's anything listed there which might have pulled in some code directly into the repository from somewhere else. If you are still unsure you can check with the team.
 -   [ ] Create a PR from your branch  **`bump-release-[YYYY.minor]`** to `main`. Add the `"no change-log"` tag to the PR so it does not show up on the release notes before merging it.
 
@@ -141,4 +140,4 @@ NOTE: this PR should make all CI relating to `main` be passing again (such as th
 ## Prep for the _next_ release
 
 -   [ ] Create a new [release plan](https://raw.githubusercontent.com/microsoft/vscode-python/main/.github/release_plan.md). (🤖)
--   [ ] [(Un-)pin](https://help.github.com/en/articles/pinning-an-issue-to-your-repository) [release plan issues](https://github.com/Microsoft/vscode-python/labels/release%20plan) (🤖)
+-   [ ] [(Un-)pin](https://help.github.com/en/articles/pinning-an-issue-to-your-repository) [release plan issues](https://github.com/Microsoft/vscode-python/labels/release-plan) (🤖)