Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
extensionKind list in product.json both for stable and insiders, see this tracking issue. verification-needed or on-testplan labelsmoke-test and fixed endgame mastercandidate)smoke-test and fixed endgame masterinsider builds endgame master--stable-build argument 鈿狅笍 )v<Major>_<Minor>.md in this repo directoryNOT MERGED - PLS REVIEW. endgame masterrelease/<x.y> endgame masterInsider from release/<x.y> endgame masterInsider endgame masterscripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented.Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame. endgame master
HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) endgame masterinsider builds endgame masterswapping with @chrmarti for buddy role.
is setting sync going to be released as part of this release?
Is the OSS build tool link private?
@sanket-bhalerao I don't think so, it's still disabled in Insider builds...but it's mentioned in the changelog.
@Stanzilla, i saw that, raised a bug for this.
so created another #91882
@sanket-bhalerao I guess the release notes in Insiders aren't formally released yet, so are subject to change.
@sanket-bhalerao I guess the release notes in Insiders aren't formally released yet, so are subject to change.
Seeing it another way, when 1.43 releases (probably later this week) its release notes will tell 1.43 users that they can get a preview of Settings Sync in the Insiders release, which by then will be 1.44.0-insider.
@sanket-bhalerao We are preparing release notes for next major release (1.43.0) (1.44.0) and we are making Settings Sync ready for preview from next insiders (1.44.0-insiders). I was completely forgotten that current insiders picks up this release notes. I will update the release notes and mention from which insiders it will be available from.
Sorry for the confusion.
@sanket-bhalerao We are preparing release notes for next major release (1.44.0) and we are making
Typo there. The next major release @sandy081 is referring to is 1.43.0
@sandy081 thanks for the update,
@gjsjohnmurray thanks for the clarification.
@gjsjohnmurray Thanks for the correction. Updated my comment.
release notes are collected in a file named
Month_Year.md
Your endgame template still quite outdated (:
@gudvinr updated the issue and template 馃憤
Is it possible to use the last day as "expected release date", because It's usually published later:
March 4 Expected release date (this may change)
Wednesday/Thursday
- [ ] Build stable for all platforms endgame master
- [ ] ...
Wednesday - March 4
Thursday - March 5
- March 4 Expected release date (this may change)
+ March 5 Expected release date (this may change)
Also using a link to the release notes document instead of repository:
- https://github.com/Microsoft/vscode-docs/tree/vnext/release-notes
+ https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_43.md
https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_43.md
What is the hold up here?
Released this yesterday.
@nicholasengleman sometimes things get delayed due to bugs we find late or issues we hit during release.
@usernamehw added the expected release day note, I'm not changing the link to the release notes md though as that would require yet another thing for the endgame master to do every month.
Most helpful comment
What is the hold up here?