diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-13 18:10:16 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-13 18:10:16 +0300 |
commit | b0b94ea6e54f824d02840912f7086e9f47350571 (patch) | |
tree | cce02fc375060d27953087b4f1f05128b0d26ce6 /doc/architecture | |
parent | 447ad69728c0cb35db1190694f29806cf7c59a88 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/architecture')
-rw-r--r-- | doc/architecture/blueprints/new_diffs.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/architecture/blueprints/new_diffs.md b/doc/architecture/blueprints/new_diffs.md index f8adcda573b..b5aeb9b8aa8 100644 --- a/doc/architecture/blueprints/new_diffs.md +++ b/doc/architecture/blueprints/new_diffs.md @@ -37,6 +37,22 @@ optional. - What is out of scope for this blueprint? --> +### Priority of Goals + +In an effort to provide guidance on which goals are more important than others to assist in making +consistent choices, despite all goals being important, we defined the following order. + +**Perceived performance** is above **improved maintainability** is above **consistent coverage**. + +Examples: + +- a proposal improves maintainability at the cost of perceived performance: ❌ we should consider an alternative. +- a proposal removes a feature from certain contexts, hurting coverage, and has no impact on perceived performance or maintanability: ❌ we should re-consider. +- a proposal improves perceived performance but removes features from certain contexts of usage: ✅ it's valid and should be discussed with Product/UX. +- a proposal guarantees consistent coverage and has no impact on perceived performance or maintainability: ✅ it's valid. + +In essence, we'll strive to meet every goal at each decision but prioritise the higher ones. + ## Proposal <!-- |