Google plans work per-quarter, using the OKR (Objective/Key-Result) framework.
improving write latencies
Use multiple fidelity modes and webworkers to speed up “expand all diffs” and “large file with many diffs” use cases.
Use them fully on gerrit-review.googlesource.com, android-review.googlesource.com and chromium-review.googlesource.com.
for managing and reviewing multiple, grouped changes
Design browser-based push notifications to reduce review latency. Let reviewers suggest rather than make edits, leading to less lost approvals.
Fix JGit and CGit merge discrepancies.
A data migration has cleaned all traces of personal data (name, email) in review metadata.
This is now possbile since we moved off of the old diff cache.
We want Git pushes where users currently bypass Gerrit to go through Gerrit as well. We suspect that performance (pushes being slow) is the main reason for bypassing. If so, we want to root cause slowness and fix it if possible.
Use them fully on gerrit-review.googlesource.com, android-review.googlesource.com and chromium-review.googlesource.com.
Provide a page for reviewing multiple changes (“topics”), providing among others batch actions and maybe diffs across projects/changes.
all of Polymer, and get rid of or re-implement all mixins
client models will centralize state-management, making the UI more dependable. Dependency injection avoids global variables, enabling multiple changes on a single page
Gerrit stops persisting personal data (name, email) in review metadata.
Private user actions (writing drafts, adding stars) cause a change reindex. This is expensive and slows down user actions. Get this data directly from All-Users to avoid the indexing step.
Gerrit continues processing after the user hangs up. We want to solve this for Google, but maybe we can fix it for Gerrit open source as well.
The Gerrit UI supports reviewing image files (including visual diffs)
Improve diff rendering performance and memory usage on many / large files.
Currently Gerrit indices are per-datacenter, and replicated asynchronously. Create a design where the index document is created together with the ref update, so it can be replicated together with the Git data, thus avoiding inconsistencies between index and git data.
Finish diff cache rollout, and migrate to Caffeine.
Implement https://gerrit-review.googlesource.com/c/homepage/+/279176, and roll it out to Gerrit, Chrome & Android.
Provide a page for reviewing multiple changes (“topics”), providing among others batch actions and maybe diffs across projects/changes.
**Calendar integration: **extension point for FE plugins surfacing calendar data
Push notifications: Design proposal, work estimation, and prototype for browser push notifications directly from Gerrit using web workers (milutin)
Code review dashboard: Gerrit users can understand their personal code review performance in a dashboard as described in Gerrit Code Review Metrics for Individuals (mharbach)
Finish CI result tab: onboarding documentation, create a Jenkins based plugin and remove the old checks plugin from googlesource.com.
Various items:
Gerrit CI will then be able to check that Polymer bindings are valid in HTML templates and that Polymer observers and computed Polymer properties have the correct type.
note: Any Google-specific OKRs will be removed prior to publishing