Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restyle Update PROJECT_FLOW with new issue thinking #448

Closed
wants to merge 2 commits into from
Closed

Restyle Update PROJECT_FLOW with new issue thinking #448

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
582c0ff
Update PROJECT_FLOW with new issue thinking
Apr 21, 2020
9f8f68c
Restyled by prettier-markdown
restyled-commits Apr 21, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 20 additions & 8 deletions docs/PROJECT_FLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,17 +38,29 @@ PR Don'ts:

### Milestones

In CHIP parlance, a milestone is simply an expected due date or release.
In CHIP parlance, a milestone is simply a tag for an expected due date or
release. Milestones are intended to help contributors and their managers to
prioritize work. There are 2 types: Date-based and Release-based.

Date-based milestones start with an "M" and have the form M3, M3.2, M4, etc.
corresponding to the number of months since January 1, 2020, and generally mean
the last Friday of that month. E.g. M1 corresponds to EOB January 24,
#### Date-based

2020. The Morrow milestone is a special milestone that means "unprioritized" or
"unscheduled" or "unscoped".
Date-based milestones are named for their due date, typically a Friday of some
week. Date-based milestones are normally assigned based on a guess about when
something's likely to bubble up and get done based on current work load and
resourcing. They are wishes, guesses.

The form of the names of release-based milestone names are TBD, and may have
flexible or changing dates.
#### Release-based

Release-based milestones are named for the release version and may have flexible
or subject-to-change due dates. Release-based milestones are intended to track
release blockers.

A special "Not sure when" milestone is a marker for issues whose priority,
scope, or blocking status have not been determined. Monthly review of these is a
project goal.

Issues without milestones are those that have yet to be considered for one of
the above. Weekly review of new issues is a project goal.

### Projects

Expand Down