wbrawner/thunderbird-android
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
thunderbird-android/docs/architecture/adr
History
Wolf-Martell Montwé 627145ef01
Add ADR 0003 - Switch Test Assertions from Truth to AssertK
2023-10-12 10:30:13 +02:00
..
0000-adr-template.md Add ADR readme and template 2023-10-05 17:14:00 +02:00
0001-switch-from-java-to-kotlin.md Add ADR 0001 about Java to Kotlin switch 2023-10-05 17:15:04 +02:00
0002-ui-wrap-material-components-in-atomic-design-system.md Changed ADR 0002 from proposed to accepted 2023-10-06 11:09:55 +02:00
0003-switch-test-assertions-from-truth-to-assertk.md Add ADR 0003 - Switch Test Assertions from Truth to AssertK 2023-10-12 10:30:13 +02:00
README.md Add ADR readme and template 2023-10-05 17:14:00 +02:00

README.md

Architecture Decision Records

This folder contains the architecture decision records (ADRs) for our project.

ADRs are short text documents that serve as a historical context for the architecture decisions we make over the course of the project.

What is an ADR?

An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences. ADRs record the decision making process and allow others to understand the rationale behind decisions, providing insight and facilitating future decision-making processes.

Format of an ADR

We adhere to Michael Nygard's ADR format proposal, where each ADR document should contain:

  1. Title: A short descriptive name for the decision.
  2. Status: The current status of the decision (proposed, accepted, rejected, deprecated, superseded)
  3. Context: The context that motivates this decision.
  4. Decision: The change that we're proposing and/or doing.
  5. Consequences: What becomes easier or more difficult to do and any risks introduced as a result of the decision.

Creating a new ADR

When creating a new ADR, please follow the provided ADR template file and ensure that your document is clear and concise.

Directory Structure

The ADRs will be stored in a directory named docs/adr, and each ADR will be a file named NNNN-title-with-dashes.md where NNNN is a four-digit number that is increased by 1 for every new adr.

ADR Life Cycle

The life cycle of an ADR is as follows:

  1. Proposed: The ADR is under consideration.
  2. Accepted: The decision described in the ADR has been accepted and should be adhered to, unless it is superseded by another ADR.
  3. Rejected: The decision described in the ADR has been rejected.
  4. Deprecated: The decision described in the ADR is no longer relevant due to changes in system context.
  5. Superseded: The decision described in the ADR has been replaced by another decision.

Each ADR will have a status indicating its current life-cycle stage. An ADR can be updated over time, either to change the status or to add more information.

Contributions

We welcome contributions in the form of new ADRs or updates to existing ones. Please ensure all contributions follow the standard format and provide clear and concise information.