-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024 April Endgame #15603
Comments
Download VS Code RC from here https://builds.code.visualstudio.com/builds/stable Tip: You can use the dev containers in the this repo for testing against linux (just open the repo and use thd command
|
Download VS Code RC from here https://builds.code.visualstudio.com/builds/stable Tip: You can use the dev containers in the this repo for testing against linux (just open the repo and use thd command
|
Thursday
Friday
Critical
andHigh
priority issues as others will be addressed in thedebt
week.Instructions on updating
npm
dependencies inpackage.json
&package-lock.json
can be found here.release/release-YYYY.MM
.main
with the following changes... (Warning: this should happen right after creating the release branch. If this is deferred till later, themain
andrelease
branches can diverge significantly, which may cause merge conflicts.)main
to the next monthly ("YYYY.M.0") version number (e.g. if the latest is2022.2.0
, bump it to2022.3.0
).npm install
to updatepackage-lock.json
Monday (Debt/Release week)
release/release-YYYY.MM
branchPublish Extension
, you do not need an approval to build the VSIX.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
)main
and cherry-picked torelease
branchSatelite extensions/npm packages
zeromq-prebuilt
Tuesday
Publish
stage of the last Stable pipeline that's successfully sanity tested.Publish
Stage of the stable pipeline linked above.endgame_plan.md
file to make it clear for the next releaseWednesday/Thursday (Day of VS Code releasing the next insider version)
main
branch to point to the next version. For example, from1.58.0
to1.59.0
As needed
release/release-YYYY.MM
branchYYYY.MM.0
, then hot fix will beYYYY.MM.1
YYYY.MM.1
, then hot fix will beYYYY.MM.2
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
)Publish
Stage of the stable pipeline linked above, and manually add one using:git tag -a YYYY.MM -m YYYY.MM -s -f
The text was updated successfully, but these errors were encountered: