This repository was archived by the owner on Jan 12, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 703
Sprint Process
liuche edited this page Oct 25, 2017
·
30 revisions
Focus follows a 2-week sprint cycle with 6-week milestone releases. Dot-releases with bugfixes are released every two weeks.
- P1: Open engineering issues for current (2-week) sprint
- P2: Remaining open engineering issues for rest of (6-week) milestone
-
[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) -
[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...)
Every 2 weeks to decide what will go into the upcoming sprint, i.e., 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.
Plan and prioritize features.