-
Notifications
You must be signed in to change notification settings - Fork 275
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
Start to keep Architectural Decision Records (ADRs) for tuf reference implementation #1182
Conversation
6a67cda
to
ffe75f2
Compare
I think you're right! We did remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look great. Once the AppVeyor issue is resolved I think it's good to go.
In order to make decisions about the code and the design explicit and easier to reference in future we want to record significant architectural decisions. This commit introduces docs/adr with a template Architectural Decision Record and index using the [MADR](https://adr.github.io/madr/) format. It also adds ADR 0000 to document the decisions to use MADR. Fixes theupdateframework#1141 Signed-off-by: Joshua Lock <[email protected]>
Signed-off-by: Joshua Lock <[email protected]>
Document the decision drop support for EOL Python versions, most notable Python 2.7 Fixes theupdateframework#1125 Signed-off-by: Joshua Lock <[email protected]>
ffe75f2
to
71de3f6
Compare
Provide additional context to clarify where we expect Python 3.6+ to be used exclusively (new modules) and link to other discussions around the future of Python 2.7 supporting code. Signed-off-by: Joshua Lock <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mille grazie, @joshuagl!
Fixes #1141, #1125
Description of the changes being introduced by the pull request:
Add initial Architectural Decision Records (ADRs) documenting some workflow decisions before the refactor:
Please verify and check that the pull request fulfills the following
requirements: