Add Satelite extensions/npm packages release plan (#14576)

to endgame plan

.github/endgame_plan.md

@@ -40,6 +40,42 @@
 - [ ] Candidate bug fixes found from sanity test should be checked into `main` and cherry-picked to `release` branch
   - After a candidate fix is merged, a pre-release build can be released by manually running [the pre-release devops pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=283) against the release branch.
 
+### Satelite extensions/npm packages
+- [ ] Reach out to the owners of each of these to coordinate the releases (if any).
+- JupyterHub (@DonJayamanne)
+    - No need to pin VS Code engine
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=521&_a=summary))
+    - PreRelease directly from main branch manually ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=520))
+- Jupyter (Notebook) Renderers (@DonJayamanne)
+    - No need to pin VS Code engine (unless you want to test something against VS Code insiders and not ship to stable users)
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=285))
+- Jupyter Powertoys (@DonJayamanne)
+    - No need to pin VS Code engine (unless you want to test something against VS Code insiders and not ship to stable users, e.g. depends on some new Jupyter Extension API)
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=305))
+- Jupyter Cell Tags (@rebornix)
+    - No need to pin VS Code engine
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=388))
+- Jupyter KeyMap (@rebornix)
+    - No need to pin VS Code engine
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=260))
+- Tensorboard (@DonJayamanne)
+    - No need to pin VS Code engine
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=531))
+    - PreRelease directly from main branch manually ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=530))
+- zeromq-prebuilt (@DonJayamanne)
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=466))
+    - Release by adding a git tag and pushing it upstream (e.g. 6.0.0-beta.16.8)
+    - Can test bundles by manually running and publishing releases to github releases (download and test the bundles manually from github releases)
+- @vscode/zeromq (@DonJayamanne)
+    - To be done after relesing `zeromq-prebuilt`
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=469))
+- @vscode/jupyter-extension (@DonJayamanne)
+    - Release directly from main/relese branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=519&_a=summary))
+- Gather (@DonJayamanne)
+    - No need to pin VS Code engine
+    - Release directly from main branch ([pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=290))
+-
+
 ## Tuesday
 - [ ] Make sure [Component Governance](https://dev.azure.com/monacotools/Monaco/_componentGovernance/191876) is happy
 - [ ] Release
@@ -60,7 +96,7 @@
   * If released version is `YYYY.MM.100`, then hot fix will be `YYYY.MM.110`
   * If released version is `YYYY.MM.110`, then hot fix will be `YYYY.MM.120`
 - [ ] Verify all candidate issues
-- [ ] Sanity test release candidate VSIX against VS Code RC  
+- [ ] Sanity test release candidate VSIX against VS Code RC
   Tip: You can use the dev containers in the this repo for testing against linux (just open the repo and use thd command `Dev Containers: Reopen in Container`)
   - [ ] Windows
     - [ ] win32-x64