Milestone Duration

• May 11, 2024–Jun 14, 2024 (May 11th is a Saturday)

Our Focus

1. Enhance user experience and enable personalization of code suggestions in VS Code and JetBrains.
   1. VS Code Code Suggestions: Cycle through code suggestions
   2. JetBrains Code Suggestions: Secret Redaction & Caching Code Suggestions
      1. Integrate Language Server into JetBrains plugin
   3. JetBrains Code Suggestion Improvements: Code Suggestion Indicators
2. Integrations:
   1. Duo Chat in Visual Studio

Our Planning Board

• Milestone 17.1 Planning Board

Issues

• Our PM has earmarked issues as workflowready for development 👉🏾 handbook
• These issues, which are listed below, are our top priorities for Milestone 17.1
• Each issue has been (or will be assigned) the Deliverable or Stretch label during this Milestone.

Capacity

• We have 96% team availability with an estimated weight budget of 46
• Note to Engineers:
  • If you have not assigned weights to your issues, please do so by Wednesday May 15th at 12pm PST.
  • Please see the 👉🏾 handbook for estimate guidance.

Team Weight - 43 of 46 assigned.

• VS Code: 4 [weight on 1 issue is pending ]
• Visual Studio: 1
• JetBrains: 26
• Neovim: 0
• Language Server: 12

Editor Extension Release Schedule for 17.1

Starting in Milestone 17.1, we are establishing a release cadence for the following editor extensions

JetBrains

• Please see 👉🏾 the JetBrains Release Schedule Issue for details on the process.

VS Code

• Please see 👉🏾 the VS Code Release Schedule MR (WIP) for details on the process.

Checklist

• Product to mark issues as workflowready for development before the 4th of the month
• Product to add themes & outcomes to the planning issue
• EM to identify the available capacity for the milestone
• PM to add workflowready for development issues
• EM to add Deliverable or Stretch to the issues
• Refine the issues already assigned to the current milestone for correct label hygiene
• Check/update past milestones for wayward issues
• Add security items
• Add bugs
• Carefully check planning priority items for customers are scheduled or well communicated

Stable counterparts

• Technical Writing ( @aqualls)

(improve this template?)