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

Jump to bottom

Show results on 2019 Q4 Distribution team OKRs #433

Merged
merged 3 commits into from
Jan 7, 2020
Merged

Show results on 2019 Q4 Distribution team OKRs #433

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
07b5dbf
Update Q4 Core Services OKR outcomes
Dec 4, 2019
7020bc5
Show results on 2019 Q4 Distribution team OKRs
slimsag Dec 5, 2019
0c20ae0
Update company/okrs/2019_q4.md
slimsag Dec 5, 2019
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
Prev Previous commit
Update company/okrs/2019_q4.md 
Co-Authored-By: Beyang Liu <beyang@sourcegraph.com>
  • Loading branch information
@slimsag @beyang
slimsag and beyang committed Dec 5, 2019
commit 0c20ae08072577ae1b2a6fc34e723731369527b3
2 changes: 1 addition & 1 deletion company/okrs/2019_q4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
1. VP Eng KR: 100% of monthly releases ship on time.
1. VP Eng KR: No tier 1 or 2 customers are blocked from upgrading to a monthly release once it ships.
1. **Distribution: Automate time-consuming ops and support tasks.**
1. Distribution KR: Major/minor and patch releases take 1 hour (including general QA but excluding customer-specific testing). => QA has been fully automated and releases are possible in under an hour. In practice, a 1 hour release has not yet happened due to QA finding release blockers.
1. Distribution KR: Major/minor and patch releases take 1 hour (including general QA but excluding customer-specific testing). => QA has been fully automated and releases are possible in under an hour. In practice, a 1 hour release has not yet happened due to QA finding release blockers. [RFC 86](https://docs.google.com/document/d/1mbnLHBhEPT2c8ttoxQaQRstivW0JIbKHKtjg-ZRr5WM/edit) addresses how to amortize QA over PRs to eliminate release blockers so that releases can take under an hour.
1. Distribution KR: All customer specific testing is complete within 2 business days of tagging any release. => Now relying primarily on automated QA for most customer testing, excluding a few which did not happen in 2 business days but did take <24h to complete at a later date.
1. **Distribution: Streamline technical blockers for tier-1 customers advancing toward general availability.**
1. Distribution KR: Address all rollout-blocking issues within 1 iteration of reporting. => Unclear to me @slimsag what issues fall under this KR, this has been modified from what I saw we agreed upon ("1 iteration of reporting" vs. by Q1?)
Expand Down