paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 18 Packages Projects Releases Wiki Activity

docs/adrs: remove status

Browse Source
This commit is contained in:
Patrik Oldsberg
2021-01-19 09:55:11 +01:00
parent 85d864c19f
commit b473cf08b5
6 changed files with 10 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-decisions/adr000-template.md
-4
View File
@@ -4,10 +4,6 @@ title: ADR000: [TITLE]
description: Architecture Decision Record (ADR) for [TITLE] [DESCRIPTION]
---
| Created | Status |
| ---------- | ------ |
| YYYY-MM-DD | Open |
# ADR000: [title]
<!-- These documents have names that are short noun phrases. For example, "ADR001: Deployment on Ruby on Rails 3.0.10" or "ADR009: LDAP for Multitenant Integration" -->
docs/architecture-decisions/adr001-add-adr-log.md
+10 -6
View File
@@ -4,12 +4,16 @@ title: ADR001: Architecture Decision Record (ADR) log
description: Architecture Decision Record (ADR) logs as a reference point for the team
---
| Created | Status |
| ---------- | ------ |
| 2020-04-26 | Open |
## Decision
## Decision: A decision was made to store ADRs in a log in the project repository
A decision was made to store ADRs in a log in the project repository
## Discussion: There is a need to store big decisions made in a log as a reference point for the team, help with onboarding new members and give context to others interested in the project.
## Discussion
## Risks: People stop adding ADRs to the log and context gets lost
There is a need to store big decisions made in a log as a reference point for
the team, help with onboarding new members and give context to others interested
in the project.
## Risks
People stop adding ADRs to the log and context gets lost
docs/architecture-decisions/adr002-default-catalog-file-format.md
-4
View File
@@ -4,10 +4,6 @@ title: ADR002: Default Software Catalog File Format
description: Architecture Decision Record (ADR) log on Default Software Catalog File Format
---
| Created | Status |
| ---------- | ------ |
| 2020-05-17 | Open |
## Background
Backstage comes with a software catalog functionality, that you can use to track
docs/architecture-decisions/adr003-avoid-default-exports.md
-4
View File
@@ -4,10 +4,6 @@ title: ADR003: Avoid Default Exports and Prefer Named Exports
description: Architecture Decision Record (ADR) log on Avoid Default Exports and Prefer Named Exports
---
| Created | Status |
| ---------- | ------ |
| 2020-05-19 | Open |
## Context
When CommonJS was the primary authoring format, the best practice was to export
docs/architecture-decisions/adr004-module-export-structure.md
-4
View File
@@ -4,10 +4,6 @@ title: ADR004: Module Export Structure
description: Architecture Decision Record (ADR) log on Module Export Structure
---
| Created | Status |
| ---------- | ------ |
| 2020-05-27 | Open |
## Context
With a growing number of exports of packages like `@backstage/core`, it is
docs/architecture-decisions/adr005-catalog-core-entities.md
-4
View File
@@ -4,10 +4,6 @@ title: ADR005: Catalog Core Entities
description: Architecture Decision Record (ADR) log on Catalog Core Entities
---
| Created | Status |
| ---------- | ------ |
| 2020-05-29 | Open |
## Context
We want to standardize on a few core entities that we are tracking in the