Skip to content
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.

Sign up for GitHub

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

Jump to bottom

September 2021 Endgame #133861

Closed
lramos15 opened this issue Sep 27, 2021 · 3 comments
Closed

September 2021 Endgame #133861

lramos15 opened this issue Sep 27, 2021 · 3 comments
Assignees
@lramos15 @sandy081
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
September 2021

Comments

@lramos15
Copy link
Member

lramos15 commented Sep 27, 2021 •
edited
Loading

  • September 27, 2021 Code freeze for the endgame
  • October 1, 2021 Endgame done
  • October 6, 2021 Expected release date (this may change)
Monday
Tuesday
Wednesday
Thursday
Friday
  • Pause scheduled insider builds endgame champion
  • Satellite modules/npm packages ready, version updated, smoke tested
  • All issues 🔖verified
  • Branch code to release/1.61 at 5pm PST endgame champion
  • Announce main is open for business endgame champion
  • Fixing (scrutiny sets in once branched - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • All release notes updated
  • Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the endgame champion can generate the pull request acknowledgment for all repositories at once. endgame champion
    • debug-adapter-protocol, inno-updater, jsonc-parser, language-server-protocol, lsif-node, vscode, vscode-codicons, vscode-css-languageservice, vscode-debugadapter-node, vscode-dev-containers, vscode-docs, vscode-emmet-helper, vscode-eslint, vscode-extension-samples, vscode-generator-code, vscode-hexeditor, vscode-html-languageservice, vscode-js-debug, vscode-js-debug-companion, vscode-js-profile-visualizer, vscode-jshint, vscode-json-languageservice, vscode-languageserver-node, vscode-livepreview, vscode-loader, vscode-lsif-extension, vscode-node-debug, vscode-node-debug2, vscode-pull-request-github, vscode-recipes, vscode-references-view, vscode-textmate, vscode-vsce
  • Acknowledge issue trackers from the community @chrmarti
  • Add notable fixes to the release notes all
  • When done fixing/verifying and there are changes since last build at the end of day PT
    • Build and manually release Insider from release/<x.y> endgame champion
  • Localization: Run Update VS Code Branch in the vscode-loc-drop repo with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) endgame champion
Friday/Monday
  • Polish release notes redmond
  • Fixing (only critical bugs - no string changes)
Monday - Wednesday

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame. endgame champion

Wednesday/Thursday - Expected release day (this may change)
  • Build stable for all platforms endgame champion
  • Sanity check of installable bits (server instructions)
    • Windows 32 bit @rzhao271
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
      • server 32-bit
    • Windows 64 bit @rzhao271
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
      • server 64-bit
    • Windows ARM64 @sbatten
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS
    • Linux x64
    • Linux server @chrmarti
      • x64
      • x64 Alpine
      • ARM32
      • ARM64
  • Publish website @gregvanl
  • Publish to stable endgame champion
  • Create an official release endgame champion
    • Create a tag: git tag <x.y.z>
    • Push the tag: git push origin <x.y.z>
    • Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links Example
  • Twitter announcement @chrisdias
  • Enable scheduled insider builds endgame champion
  • Bump up the version in package.json on main - endgame champion
  • Publish @types/vscode endgame champion
@lramos15 lramos15 added the endgame-plan VS Code - Next release plan for endgame label Sep 27, 2021
@lramos15 lramos15 added this to the September 2021 milestone Sep 27, 2021
@lramos15 lramos15 pinned this issue Sep 27, 2021
@isnikulin
Copy link

Excuse me, what's the "OSS tool" mentioned in the description? The link gives me 404.

@lszomoru lszomoru mentioned this issue Sep 30, 2021
Closed
@RedMickey RedMickey mentioned this issue Oct 7, 2021
Closed
@alexdima
Copy link
Member

alexdima commented Oct 7, 2021

The "OSS tool" is an internal script that we execute before releasing VS Code. The script iterates over all the OSS that we ship with VS Code and generates a ThirdPartyNotices.txt file. You can find such a file in VS Code's installation dir (or in the app bundle on macOS). The generated file is similar with the one at https://github.com/microsoft/vscode/blob/main/ThirdPartyNotices.txt but with more entries.

@lramos15
Copy link
Member Author

lramos15 commented Oct 8, 2021

1.61.0 Was released yesterday 🎉

@lramos15 lramos15 closed this as completed Oct 8, 2021
@lramos15 lramos15 unpinned this issue Oct 8, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Nov 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lramos15 lramos15

@sandy081 sandy081

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
September 2021
Development

No branches or pull requests
4 participants
@lramos15 @alexdima @sandy081 @isnikulin