Closed
Description
Release candidate (Wednesday, Jun 19)
- Ensure all new features are tracked via telemetry
- Announce the code freeze (not just to team but also to ptvsd and language server)
- Create a branch against
masterfor a pull request - Update the version in
package.json - Run
npm installto make surepackage-lock.jsonis up-to-date - Update
requirements.txtto point to latest release version ofptvsd. - Update
languageServerVersioninpackage.jsonto point to the latest version of the Language Server. - Update
CHANGELOG.md- Create a new section for this release
- Copy over the "Thanks" section from the previous release and make sure it's up-to-date
- Run
news(typicallypython news --final --update CHANGELOG.md | code-insiders -) - Touch up news entries
[ ] Add any relevant news entries for ptvsd and the language server if they were updated
- Update
ThirdPartyNotices-Distribution.txtby runningtpn(typicallypython tpn --npm package-lock.json --npm-overrides package.datascience-ui.dependencies.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt) [ ] UpdateThirdPartyNotices-Repository.txtas appropriate- Create a pull request against
master - Merge pull request into
master - Delete the
releasebranch in the repo - Create a new
releasebranch frommaster - Bump the version number to the next release in the
masterbranch-
package.json -
package-lock.json
-
- Create a pull request against master
- Merge pull request into
master - Announce the code freeze is over
[ ] Update Component Governance[ ] Provide details for any automatically detected npm dependencies[ ] Manually add any repository dependencies
- GDPR bookkeeping (@brettcannon)
- Open appropriate documentation issues
- Begin drafting a blog post (@luabud)
- Ask CTI to test the release candidate (@brettcannon)
Final (Tuesday, Jun 25)
Preparation
- Make sure the appropriate pull requests for the documentation -- including the WOW page -- are ready
- Create a branch against
releasefor a pull request - Update the version in
package.json - Run
npm installto make surepackage-lock.jsonis up-to-date (the only update should be the version number ifpackage-lock.jsonhas been kept up-to-date) - Update
CHANGELOG.md- Update version and date for the release section
- Run
newsand copy-and-paste new entries (typicallypython news --final | code-insiders -; quite possibly nothing new to add)
- Update
ThirdPartyNotices-Distribution.txtby runningtpn(typicallypython tpn --npm package-lock.json --npm-overrides package.datascience-ui.dependencies.json --config tpn/distribution.toml ThirdPartyNotices-Distribution.txt; quite possible there will be no change) - Update
ThirdPartyNotices-Repository.txtmanually if necessary - Create pull request against
release(Updates for the 2019.6.0 release. #6327) - Merge pull request into
release - Make sure component governance is happy (ignoring: 2 packages with alerts, 3 with failures)
Release
[x] Make sure CI is passing[x] Generate the final.vsixfile- Make sure no extraneous files are being included in the
.vsixfile (make sure to check for hidden files) [x] Upload the final.vsixfile to the marketplace- Publish documentation changes
- Publish the blog post (@luabud)
[ ] Create a release on GitHub (which creates an appropriate git tag)- Determine if a hotfix is needed
- Merge
releaseback intomaster(@IanMatthewHuff, @rchiodo)
Clean up after this release
- Go through
info neededissues and close any that have no activity for over a month - GDPR bookkeeping
Prep for the next release
- Create a new release plan
- (Un-)pin release plan issues