-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Decide on how to handle Bidirectional Decisions Dependencies #187
Comments
I don't think option 1 scales at all using decisions-as-issues. |
Is our decision making such a strict process that we really need to worry about this? It's fine to mention interplay between decisions. Could option 2 be "Mention in relevant arguments"? |
It's fine, it can be that and some related section like https://github.com/joelparkerhenderson/architecture-decision-record/tree/main/locales/en/examples/programming-languages#related |
Nah yeah you're right, a link and a short description of how the current decision is related to another suffices would be nice. |
Add your confidence scores then move to Done. |
yes, this makes sense |
Deciders & Confidence:
Last updated: [DD-MM-YYYY]
Context
Decision Drivers
Considered Options
Impacts & Dependencies sections
Example
Related section
https://github.com/joelparkerhenderson/architecture-decision-record/tree/main/locales/en/examples/programming-languages#related
Decision Outcome
Chosen option: Related section
Reason: The alternative is more time consuming to setup properly
The text was updated successfully, but these errors were encountered: