Title: Theory / Important / Chrome / Release
On every note of this deck, unless a note says otherwise:
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md

Name: A release blocker
Definition: A bug such that Chrome must not be shipped with it
Context: Chrome

Question: Who can mark a bug as release blocker
Answer: Every team member
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What to take into account to determine if a bug is a release blocker?
Answer: severity
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome
Answer2: prevalence

Question: What to do when creating a release blocker
Answer: give a detailled rationale
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome
Answer2: tag OS and milestone

Constant: ReleaseBlock-(Dev|Beta|Stable)
Meaning: Note that the bug block release to dev|beta|stable
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Language: Objective-C
Context: Chrome tag

Name: A critical bug
Definition: A bug with extreme consequence to the user,
Context: Chrome
Example: regression in privacy (leaking user data),
Example2: loss of user data, crash on startup, etc.
Intuition: These bugs must be fixed immediately and thus should block any release where they are present.

Name: A high severity bug
Definition: A bug with large impact to the user,
Context: Chrome
Example: CSS rendering issue causing content to disappear,
Example2: videos not playing,
Intuition: no simple workaround for the issue.
Example3: extreme jank,

Name: A medium severity bug
Definition: A bug with moderate impact to the user,
Context: Chrome
Example: CSS rendering issue causing content to be misaligned
Example2: memory regressions,
Intuition: There may be a workaround for the issue.
Example3: moderate jank,
Example4: non-startup crash,

Name: A low severity bug
Definition: A bug with little impact to the user, generally cosmetic in nature and easy to work around.
Context: Chrome

Question: What is the severity of regression in privacy
Answer: critical
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of loss of user data
Answer: critical
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of crash on startup
Answer: critical
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of css causing content to disappear
Answer: high
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of video not playing
Answer: high
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of CSS rendering issues causing content to be misaligned
Answer: Medium
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of moderate jank
Answer: Medium
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of non-startup crash
Answer: Medium
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Question: What is the severity of memory regression
Answer: Medium
Page: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/process/release_blockers.md
Context: Chrome

Name: Severity of a bug
Definition: The kind of impact it has on user's use of the software
Context: Chrome

Name: prevalence of a bug
Definition: The percentage of the user base having the bug
Context: Chrome

Name: Few user
Definition: At most 5%
Context: Chrome, bug prevalence

Name: Some user
Definition: Between 5% and 35% of users
Context: Chrome, bug prevalence

Name: Most user
Definition: Between 35% and 75% of users
Context: Chrome, bug prevalence

Name: All user
Definition: At least 75% of users
Context: Chrome, bug prevalence

Question: What priority can have a release block
Answer: P0 or P1
Page: https://www.chromium.org/issue-tracking/release-block-guidelines/
Context: Chrome

Question: When can a ReleaseBlock be created
Answer: soon before release point. Otherwise, the issue is part of normal process
Page: https://www.chromium.org/issue-tracking/release-block-guidelines/
Context: Chrome

Name: Sheriff
Definition: people in charge of ensuring Chromium build infrastructure is doing its job of helping developers deliver good software
Page: https://www.chromium.org/issue-tracking/release-block-guidelines/
Context: Chrome

Question: The goals of Sheriff
Answer: The tree is open, because when the tree is closed nobody can make progress;
Page: https://www.chromium.org/issue-tracking/release-block-guidelines/
Context: Chrome
Answer2: New test failures are not introduced, because they weaken our assurance that we're shipping good code;
Answer3: Existing test failures are repaired, for the same reason

Question: Condition to be a sheriff
Answer: be a google employee
Page: https://www.chromium.org/issue-tracking/release-block-guidelines/
Context: Chrome
Answer2: be a Chrome comitter