Skip to content

February 2020 Endgame #91278

Description

@Tyriar
  • February 24 Code freeze for the endgame
  • February 28 Endgame done
  • March 4 Expected release date (this may change)

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

Monday
  • Run OSS tool endgame master
  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms at 5pm PT
  • Create test plan items following the template here by 5pm PT
  • Add verification-needed label to features needed testing and are not tested by TPIs.
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/
  • Create Test plan item for smoke testing (OS & browser coverage!) endgame master Test: Smoke Tests #91337
  • Review the extensionKind list in product.json both for stable and insiders, see this tracking issue.
Tuesday
Wednesday
  • 🔖Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • 🔖Verification needed
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame master
Thursday
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • 🔖Verification needed
  • 🔖Verification
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame master
Friday
Friday/Monday
  • Branch code to `release/<x.y> endgame master
  • Bump up the version in package.json - endgame master
  • Announce master is open for business endgame master
  • Polish release notes redmond
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 master

Wednesday/Thursday

Activity

  1. sandy081 commented on Feb 25, 2020

    @sandy081
    Member

    swapping with Christof Marti (@chrmarti) for buddy role.

  2. sanket-bhalerao commented on Feb 27, 2020

    @sanket-bhalerao

    is setting sync going to be released as part of this release?

  3. Techman commented on Feb 29, 2020

    @Techman

    Is the OSS build tool link private?

  4. Stanzilla commented on Mar 2, 2020

    @Stanzilla

    Sanket Bhalerao (@sanket-bhalerao) I don't think so, it's still disabled in Insider builds...but it's mentioned in the changelog.

  5. sanket-bhalerao commented on Mar 2, 2020

    @sanket-bhalerao

    Benjamin Staneck (@Stanzilla), i saw that, raised a bug for this.
    #91875 - which was closed without a proper explanation, why its in release notes if its not released.
    so created another #91882

  6. gjsjohnmurray commented on Mar 2, 2020

    @gjsjohnmurray
    Contributor

    Sanket Bhalerao (@sanket-bhalerao) I guess the release notes in Insiders aren't formally released yet, so are subject to change.

  7. gjsjohnmurray commented on Mar 2, 2020

    @gjsjohnmurray
    Contributor

    Sanket Bhalerao (@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.

  8. sandy081 commented on Mar 2, 2020

    @sandy081
    Member

    Sanket Bhalerao (@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.

  9. gjsjohnmurray commented on Mar 2, 2020

    @gjsjohnmurray
    Contributor

    Sanket Bhalerao (@sanket-bhalerao) We are preparing release notes for next major release (1.44.0) and we are making

    Typo there. The next major release Sandeep Somavarapu (@sandy081) is referring to is 1.43.0

  10. sanket-bhalerao commented on Mar 2, 2020

    @sanket-bhalerao

    Sandeep Somavarapu (@sandy081) thanks for the update,
    John Murray (@gjsjohnmurray) thanks for the clarification.

  11. sandy081 commented on Mar 2, 2020

    @sandy081
    Member

    John Murray (@gjsjohnmurray) Thanks for the correction. Updated my comment.

  12. gudvinr commented on Mar 5, 2020

    @gudvinr

    release notes are collected in a file named Month_Year.md

    Your endgame template still quite outdated (:

  13. Tyriar commented on Mar 5, 2020

    @Tyriar
    ContributorAuthor

    gudvinr updated the issue and template 👍

  14. usernamehw commented on Mar 6, 2020

    @usernamehw
    Contributor

    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

  15. johnengleman commented on Mar 6, 2020

    @johnengleman

    What is the hold up here?

  16. Tyriar commented on Mar 10, 2020

    @Tyriar
    ContributorAuthor

    Released this yesterday.

    @nicholasengleman sometimes things get delayed due to bugs we find late or issues we hit during release.

    Alexander (@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.

  17. locked and limited conversation to collaborators on Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

endgame-planVS Code - Next release plan for endgame

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions