Martin Vrachev d0fa8fc8ca Document ADR 0008 about unrecognized fields ... Even though, this ADR documents something already implied in the TUF spec in [document formats](https://theupdateframework.github.io/specification/latest/#document-formats) it seems better to document this decision clearly so that it could be referenced and give an explanation why someone can load a metadata file with additional unrecognized fields. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>		2021-04-14 13:51:55 +03:00
..
0000-use-markdown-architectural-decision-records.md	docs/adr: start to keep ADRs in MADR format	2020-10-26 16:26:52 +00:00
0001-python-version-3-6-plus.md	ADR0001: clarify when/where Python 3.6+ is expected	2020-10-27 11:25:42 +00:00
0002-pre-1-0-deprecation-strategy.md	ADR0002: document deprecation strategy post 1.0	2020-11-24 15:26:51 +00:00
0003-where-to-develop-TUF-1-0-0.md	ADR003: Add pros and cons of the options	2020-11-27 12:26:52 +02:00
0004-extent-of-OOP-in-metadata-model.md	ADR0004: Justify extent of OOP in metadata model	2020-11-30 14:59:56 +01:00
0005-use-google-python-style-guide.md	Add style guide usage instructions to ADR0005	2020-12-04 10:50:36 +01:00
0008-accept-unrecognised-fields.md	Document ADR 0008 about unrecognized fields	2021-04-14 13:51:55 +03:00
index.md	ADR0005: Decide on python code style guide	2020-12-04 10:39:24 +01:00
template.md	docs/adr: start to keep ADRs in MADR format	2020-10-26 16:26:52 +00:00