Skip to content

Latest commit

 

History

History
72 lines (47 loc) · 4.78 KB

Issue-Tracking.md

File metadata and controls

72 lines (47 loc) · 4.78 KB
Raw

This page describes how we track issues in the vscode repository.

Popular queries

Inbox tracking and Issue triage

New issues or pull requests submitted by the community are triaged by a team member. The team rotates the inbox tracker on a weekly basis. A bot assists the inbox tracker.

Inbox Tracking

The inbox tracker is responsible for the global inbox containing all open issues and pull requests that

  • are neither feature requests nor test plan items nor plan items and
  • have no owner assignment.

The inbox tracker may perform any step described in our issue triaging documentation but it's main responsibility is to route issues to the actual feature area owner.

Feature area owners track the feature area inbox containing all open issues and pull requests that

  • are personally assigned to them and are not assigned to any milestone
  • are labeled with their feature area label and are not assigned to any milestone. This secondary triage may involve any of the steps described in our issue triaging documentation and results in a fully triaged or closed issue.

Ongoing Issue Management

The details can be found in our issue triaging documentation.

Planning

During the iteration planning process we use the following sources as input:

  • Review feature requests with many reactions. Issues we plan to work on during an iteration are assigned to the current milestone.

Filing bugs as a development team member

When team members files a bug they perform steps of the inbox tracker for the issue they filed. Therefore bugs filed by the development team do not need to be triaged by the global inbox tracker.

Verification

Issues need to be verified.

Verification is a service that you request from others either implicitly with the bug-label or explicitly with the verification-needed-label. Find issue that are to be verified with these queries

Follow the these rules:

  1. Query for issues that are to be verified
  2. Start with issues you created (filter by Author) but didn't close
  3. Pick an item
    • Start with setting verified-label (prevents duplicate verifications)
    • Verify the issue
    • If you cannot verify the issue due to missing or hard-to-understand repro steps, add a verification-steps-needed label and remove the verified label
    • If the issue still shows, add the verification-found-label and remove the verified label
    • Go back to #3

Consistent labels across vscode repositories

Visual Studio Code consists of multiple repositories and we should use consistent work flows and labels across all our repositories.

To establish consistent labels across all our repositories use the Label Manager tool.

Consistent milestones across vscode repositories

To enable planning across repositories all the Visual Studio Code related repositories need to define the same milestones.

Iteration Planning

We use issues for iteration plans. Iteration plans have a label iteration-plan with tasks [ ] for the different items. The individual items are tracked in existing issues (bugs, feature requests). If there is no existing issue then a new issue with the label plan-item is created. All our iteration plans can be found here