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 Endgame #44419

Closed
sandy081 opened this issue Feb 26, 2018 · 5 comments
Closed

February Endgame #44419

sandy081 opened this issue Feb 26, 2018 · 5 comments
Assignees
@sandy081
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
February 2018

Comments

@sandy081
Copy link
Member

sandy081 commented Feb 26, 2018 •
edited by Tyriar
Loading

Endgame Schedule

  • Feburary 26, Code freeze for the endgame
  • March 2, Endgame done

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

Monday

Tuesday

Wednesday

Thursday

  • Fixing last issues
  • Verification needed
  • Verification
  • Run OSS tool endgame master
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
    • do not forget to update the distro attribute in the package.json with the commit ID of the distro repo.
    • Create list for team members to enter new OSS usage into the OSS registry endgame master

Friday

Friday or Monday week 2

  • Disable continuous insider builds - endgame master
  • Branch code to release/<x.y> and release master - endgame master
  • Bump up the version in package.json - endgame master
  • Announce master is open for business endgame master
  • Polish release notes @gregvanl

Monday week 2 - Wednesday week 2

Thursday/Friday week 2

  • Merge translations PR (if it makes it in time) endgame master
  • Build stable for all platforms endgame master
  • Make rpm signing request @Tyriar
  • Sanity check of installable bits
  • Publish website @gregvanl
  • Publish to stable @owner
  • Publish deb and rpms to repositories manually @Tyriar
  • Add version with symbols to HockeyApp @Tyriar
  • Add a git tag to HEAD of release/<x.y> in format x.y.z endgame master
  • Enable scheduled insider builds endgame master
  • Twitter announcement @seanmcbreen

DONE
@sandy081 sandy081 added the endgame-plan VS Code - Next release plan for endgame label Feb 26, 2018
@sandy081 sandy081 added this to the February 2018 milestone Feb 26, 2018
@sandy081 sandy081 self-assigned this Feb 26, 2018
@kieferrm kieferrm mentioned this issue Mar 2, 2018
Closed
45 tasks
@ZanderBrown
Copy link

It's quite frustrating that vscode installed by rpm through the repo is notifying me of an update when it isn't available in the repo.

Perhaps code installed this way shouldn't show update notifications and leave that to the package manager (alternately speed up the upload process)

@lynchem
Copy link

lynchem commented Mar 14, 2018

Publish deb and rpms to repositories manually

A week after release and I still don't have the Feb build available via rpm. Can this be automated for the future? Could we get the current one up there?

@Tyriar
Copy link
Member

Tyriar commented Mar 14, 2018

@lynchem we're having issues with the internal service used to publish the rpm and are working with the team that owns that to resolve it. Automating this would be a huge weight off my shoulders every month but it's not currently possible.

@ZanderBrown
Copy link

@Tyriar understand it can be hard but the 'an update is available' notification every time a window is opened gets frustrating, especially when I actually want to update

@Tyriar
Copy link
Member

Tyriar commented Mar 14, 2018

@ZanderBrown see #43671

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sandy081 sandy081

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

No branches or pull requests
4 participants
@Tyriar @sandy081 @lynchem @ZanderBrown