AML Extension: Iteration Plan for November 2022

[tbombach]

Schedule

• Oct 30th - Nov 4th: Tech debt/iteration planning
• Nov 7th - Nov 22nd: Development/feature work
• Nov 23rd - Nov 25th: Endgame/bug fixes
• Nov 28th - Dec 2nd: Tech debt/iteration planning

OOF

• @shsuman - Nov 21^st - Nov 25^th

Plan Items

Goals

• Support preview release for interactive jobs
• Polish and raise quality bar for YAML editing and getting started experiences

Legend

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Web Connection Experience

• Set up monitoring tests for vscode.dev clickout #1799 @tbombach and @sevillal
• 🏃 Preserve active file context when clicking out from notebook editor #1800 @sevillal and @tbombach
• [Web] Investigate preserving selected kernel from Studio notebook editor to vscode.dev connected experience #1801 @sevillal

Desktop Web Connection Experience

• 🏃 Refactor Desktop clickout to use Tundra's websocket-tcp bridge #1786 @sevillal

Q&R Getting Started

• 🏃Problem signing into Azure ML using VSCode with latest version #1745
• [Design Discussion] Default workspace service activation on-demand vs at extension activation (& sessionsChanged) #1555 @sevillal
• Implement VS Code walkthrough feature based on retention analysis #1847

YAML editing

• [Discuss] Improve YAML execution experience and discoverability #1790 @shsuman
• Filter Anonymous Environments in Tree View #1758 @shsuman
• [Investigate] Support for long URI format in YAML files #1794 @shsuman
• Remove file: prefix from local path completions in yaml #1795 @shsuman
• 💪 Support for validating long URI formats [ARM ID] in Yaml files #1803 @shsuman
• Pass invoker info (user-agent) to CLI via environment variable during CLI invocation #1400 @shsuman
• Do not validate azureml:// registry format in the yaml #1772 @shsuman

Q&R Documentation

• 🏃 Remove notes about using v1.0 of the CLI from documentation. #1677 @tbombach

Customer issues

• 🏃 https://github.com/microsoft/vscode-azureml/issues/282 @tbombach
• 🏃 https://github.com/microsoft/vscode-azureml/issues/337 @sevillal

Build/Compliance

• 🏃 Transition publish pipeline off VS Code organization with Data Wrangler #1696 @tbombach
• Migrate repositories to GitHub Enterprise Cloud with Enterprise Managed User #1675 @tbombach
• https://github.com/microsoft/vscode-azureml/issues/305 @tbombach

Upstream tracking issues

• Click out from Az ML Studio to VS Code doesn't select the right environment. vscode-jupyter#11260
• Investigate switching to MSAL JS library vscode-azure-account#203
• Ensure default global interpreter used is the default python in terminal vscode-python#19818
• Show a Python 3.6 deprecation prompt when a user explicitly attempts to run using a 3.6 interpreter vscode-python#19988
• [Azure ML Tundra]Tundra's ws-tcp sends a sequence of empty messages when TCP socket is closed #1751
• [Azure ML Tundra] Fix Tundra service unexpected timeout #1767
• [Azure ML] Disable 'VS Code for Web' link on Studio when Tundra is not available or CI in on Private Link #1768
• Local path completions in environment.build.dockerFilePath & environment.build.path #1796
• [Investigate] Syntax for using curated environments has changed to include azureml registry name in Yaml files #1756
• Changes required in YAML schemas to support long uri format by the extension #1805
• Add armType: local_path in environment.build.path in the applicable schemas #1806
• Add arm_type:datastore to all the relevant datastore fields in command job schema and pipeline job schema #1807

DRI-lite Schedule

• Mon, Nov 7th - Sergio
• Mon, Nov 14th - Shantnu [Swapped]
• Mon, Nov 21th - Thomas [Swapped]
• Mon, Nov 28th - Sergio