forked from theupdateframework/python-tuf
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document the outcome of theupdateframework#1126 to develop TUF 1.0.0 in a subdirectory of the current TUF implementation. Signed-off-by: Teodora Sechkova <[email protected]>
- Loading branch information
Showing
2 changed files
with
47 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# Develop TUF 1.0.0 in a subdirectory of the current TUF implementation | ||
|
||
* Status: accepted | ||
* Date: 2020-11-23 | ||
|
||
Technical Story: https://github.com/theupdateframework/tuf/issues/1126 | ||
|
||
## Context and Problem Statement | ||
|
||
The plan is to implement a refactored TUF (1.0.0) alongside the current | ||
code base, in order to not disrupt existing usage and keep providing | ||
a Python 2.7 client. | ||
|
||
We need to decide on the best place to do this development. | ||
|
||
## Decision Drivers | ||
|
||
* Developing the new code in piecemeal | ||
This comment has been minimized.
Sorry, something went wrong. |
||
* Continuing to make releases in the interim | ||
* Avoiding maintenance overhead | ||
|
||
## Considered Options | ||
|
||
Develop TUF 1.0.0: | ||
|
||
* In its own repository | ||
* In a separate develop branch of the current TUF implementation | ||
This comment has been minimized.
Sorry, something went wrong. |
||
* In the default branch, archiving the current implementation | ||
* In a subdirectory of the current TUF implementation | ||
|
||
## Decision Outcome | ||
|
||
Chosen option: "Develop TUF 1.0.0 in a subdirectory of the current TUF | ||
implementation", because we want to add the new TUF code gradually | ||
while keep maintaining the current implementation given a limited | ||
This comment has been minimized.
Sorry, something went wrong. |
||
maintenance resources. | ||
|
||
### Negative Consequences | ||
|
||
* In progress development in the default branch causes messiness | ||
in plain sight. | ||
|
||
## Links | ||
|
||
* [Discussion of Python version support in TUF 1.0.0](https://github.com/theupdateframework/tuf/issues/1125) | ||
* [Discussion of deprecation policy for the pre-1.0, Python 2.7 supporting, code](https://github.com/theupdateframework/tuf/issues/1127) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This doesn't flow quite right. I'd suggest either: