Document the architecture decisions

[php-coder]

See for details:

• http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions
• https://speakerdeck.com/vanto/a-brief-introduction-to-architectural-decision-records
• https://adr.github.io/
• https://adr.github.io/madr/
• https://github.com/npryce/adr-tools

[php-coder]

The new label impact/adr has been introduced to mark the issues that contain architecture decisions.

[php-coder]

I've decided to use a simple document in markdown format: https://github.com/php-coder/mystamps/blob/master/docs/decisions-log.md

The logs from https://github.com/php-coder/mystamps/wiki/logbook should be migrated.

[php-coder]

The new label impact/adr has been introduced to mark the issues that contain architecture decisions.

In order to support ADR lifecycle, the label impact/adr has been renamed to ADR/needed. Also ADR/done and ADR/waiting have been introduced.