Skip to content

Draft: chore: Document architecture blueprint status descriptions

Lucas Charles requested to merge document-blueprint-statuses into master

What does this MR do and why?

While we document and validate the current statuses for blueprints, we do not describe them. This MR adds some basic descriptions.

We could also move this to handbook page but having the statuses within the same page is helpful as this is the page listing all blueprints with their current descriptions.

This also introduces a bit of duplication since now we have 3 separate lists within the codebase. TODO to reduce duplication.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading