microsoft/vscode-tools-for-ai

v0.50.0 Endgame

tbombach opened this issue · 0 comments

tbombach commented

Note: Public releases are always even numbered (e.g. 0.14.0). Nightly releases are odd numbered (0.13.0), which the build system handles automatically. When you release, make sure to bump the version to the next even number. Once that is merged, nightly releases will start releasing with the next odd number. Currently we are bumping the minor version for each release.

Checklist

1. Version bump

  • Create a release branch from version of master intended to be released. Name it "Rel#.#.#", e : Rel0.14.0
  • Update version in package.json in the release branch
  • Update CHANGELOG.md with changes made in the release branch.
  • Submit the above edits as a PR and have it reviewed.
  • Run through the Testing Checklist below to find any potential regressions using the latest pre-release version published to the marketplace (using VS Code Insiders)

2. Testing Checklist

YAML Submissions

  • Create workspace
  • Create experiment
  • Create environment
  • Create aml cluster
  • Create aml compute instance
  • Dataset new version
  • Local experiment submission
  • Remote experiment submission
  • Reference dataset during run submission
  • Update environment (e.g. changing dependencies updates the version)

Tree operations

  • View dataset properties
  • Dataset archive
  • Log streaming
  • Log / output download
  • Jupyter extension integration ("Pick how to connect to Jupyter" list and recent connection in that list)
    • [No regression] After selecting remote server there is no reload prompt or a prompt to select a new kernel (keeps executing locally). Need to manually select the appropriate remote kernel.
  • Delete workspace

Files

  • Test YAML language support
  • Test YAML template generation

Remote experience

  • Test non-standard management endpoints (e.g. gov cloud) @shsuman
  • Test public access behind vnet @sevillal

If hotfixes are required before release

  • Make the hotfix change in master, then cherry-pick it to the release branch
  • Test any affected areas from the Testing Checklist

3. Release to marketplace

  • Tag the commit in the release branch with the version number (e.g. v0.14.0). This will trigger a pipeline run in the release pipeline: https://dev.azure.com/monacotools/Monaco/_build?definitionId=320&_a=summary There is a manual review step, so this pipeline will build the release candidate, but won't release until you approve.
  • Approve the Publish step in the release pipeline to allow the pipeline to upload/publish the vsix to the marketplace.
  • Download the latest version from the marketplace (note, it may take up to 30 minutes and restarting vscode multiple times to force it to refresh the marketplace). Do a quick test to ensure the extension works as expected.