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

February 2020 Endgame #91278

Closed
Tyriar opened this issue Feb 24, 2020 · 16 comments
Closed

February 2020 Endgame #91278

Tyriar opened this issue Feb 24, 2020 · 16 comments
Assignees
@Tyriar @chrmarti
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
February 2020

Comments

@Tyriar
Copy link
Member

Tyriar commented Feb 24, 2020 •
edited
Loading

  • 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
@Tyriar Tyriar added the endgame-plan VS Code - Next release plan for endgame label Feb 24, 2020
@Tyriar Tyriar added this to the February 2020 milestone Feb 24, 2020
@Tyriar Tyriar pinned this issue Feb 25, 2020
@Tyriar Tyriar mentioned this issue Feb 25, 2020
Closed
6 tasks
@sandy081 sandy081 assigned chrmarti and unassigned sandy081 Feb 25, 2020
@sandy081
Copy link
Member

swapping with @chrmarti for buddy role.

@egamma egamma mentioned this issue Feb 25, 2020
Closed
54 tasks
This was referenced Feb 26, 2020
Closed
Closed
@bpasero bpasero mentioned this issue Feb 26, 2020
Closed
@sanket-bhalerao
Copy link

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

@Techman
Copy link

Techman commented Feb 29, 2020

Is the OSS build tool link private?

@Stanzilla
Copy link

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

@sanket-bhalerao
Copy link

sanket-bhalerao commented Mar 2, 2020 •
edited
Loading

@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

@gjsjohnmurray
Copy link
Contributor

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

@gjsjohnmurray
Copy link
Contributor

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

@sandy081
Copy link
Member

sandy081 commented Mar 2, 2020 •
edited
Loading

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

@gjsjohnmurray
Copy link
Contributor

@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

@sanket-bhalerao
Copy link

@sandy081 thanks for the update,
@gjsjohnmurray thanks for the clarification.

@sandy081
Copy link
Member

sandy081 commented Mar 2, 2020

@gjsjohnmurray Thanks for the correction. Updated my comment.

@gudvinr
Copy link

gudvinr commented Mar 5, 2020

release notes are collected in a file named Month_Year.md

Your endgame template still quite outdated (:

@Tyriar
Copy link
Member Author

Tyriar commented Mar 5, 2020

@gudvinr updated the issue and template 👍

@usernamehw
Copy link
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

@nicholasengleman
Copy link

What is the hold up here?

@Tyriar
Copy link
Member Author

Tyriar commented Mar 10, 2020

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.

@Tyriar Tyriar closed this as completed Mar 10, 2020
@kieferrm kieferrm unpinned this issue Mar 12, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

@chrmarti chrmarti

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
February 2020
Development

No branches or pull requests
10 participants
@Stanzilla @gudvinr @Tyriar @nicholasengleman @Techman @gjsjohnmurray @chrmarti @sanket-bhalerao @usernamehw @sandy081