Editor Extensions 17.1 Planning
Milestone Duration
- May 11, 2024–Jun 14, 2024 (May 11th is a Saturday)
Our Focus
- Enhance user experience and enable personalization of code suggestions in VS Code and JetBrains.
- VS Code Code Suggestions: Cycle through code suggestions
- JetBrains Code Suggestions: Secret Redaction & Caching Code Suggestions
- JetBrains Code Suggestion Improvements: Code Suggestion Indicators
- Integrations:
Our 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
17.1
Editor Extension Release Schedule for 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.
Date | Release Officer | Channel | Status | Comments |
---|---|---|---|---|
Wednesday, May 22nd | @lauraionel | Stable | Released ![]() |
https://plugins.jetbrains.com/plugin/22325-gitlab-duo/edit/versions/stable |
Tuesday, June 4th | @lauraionel | Stable | Released ![]() |
https://plugins.jetbrains.com/plugin/22325-gitlab-duo/edit/versions/stable/551186 |
VS Code
- Please see
the VS Code Release Schedule MR (WIP) for details on the process.
Date | Release Officer |
---|---|
Wednesday, May 23rd | @viktomas |
Monday, June 10th | @viktomas |
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)