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

Sprint Process

Sebastian Kaspari edited this page Nov 15, 2017 · 30 revisions

Focus follows a 2-week sprint cycle with 6-week milestone releases. Dot-releases with bugfixes are released every two weeks. Our upcoming train schedule is here.

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... or addressed label will be triaged every week, and assigned a Priority label (P1, P2, P3...)

Weekly Bug management (alternating)

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, adding to the contributor bug lists, looking at milestone lists.

Monthly Roadmap Planning

Plan and prioritize features for upcoming milestones - an update will be emailed out.

Clone this wiki locally