Skip to content
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.

Sprint Process

liuche edited this page Nov 7, 2017 · 30 revisions

Focus follows a 2-week sprint cycle with 6-week milestone releases. Dot-releases with bugfixes are released every two weeks.

Issue naming and labels

Labels

Issue Prefixes

  • [meta]: larger issues that need to be broken down, into a [breakdown] issue and issues for its smaller parts. This should include a checklist of all the issues (including the [breakdown] issue).

    These do NOT get a P* label, but should be in a milestone.

  • [breakdown]: issue to track the work of breaking down a larger bug

Triage - Weekly

All bugs that do not have a P1, P2... label will be triaged every week, and assigned a Priority label (P1, P2, P3...)

Sprint Planning/Backlog grooming - Alternating weeks

Sprint planning

Deciding what goes into a sprint, promote P2 issues to P1. After every release, this meeting is for deciding what goes into the upcoming milestone - add issues to the milestone and set them as P2.

Backlog grooming

Handling Triage overflow, or adding to the contributor bug lists, or looking at milestone lists.

Roadmap Planning - Monthly

Plan and prioritize features.

Clone this wiki locally