Skip to content

Commit

Permalink
ADR0003: where to develop TUF 1.0.0
Browse files Browse the repository at this point in the history
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
sechkova committed Nov 23, 2020
1 parent 6333a4e commit 8db81fd
Show file tree
Hide file tree
Showing 2 changed files with 47 additions and 0 deletions.
46 changes: 46 additions & 0 deletions docs/adr/0003-where-to-develop-TUF-1-0-0.md
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.

Copy link
@joshuagl

joshuagl Nov 23, 2020

This doesn't flow quite right. I'd suggest either:

  1. remove "in"

Developing the new code piecemeal

  1. expanding

Developing the new code in a piecemeal fashion

  1. replacing

Developing the new code iteratively, in parallel with the existing code

* 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.

Copy link
@joshuagl

joshuagl Nov 23, 2020

develop is the main branch name, develop->development here for clarity?

* 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.

Copy link
@joshuagl

joshuagl Nov 23, 2020

"while we keep maintaining the current implementation given limited" ?

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)
1 change: 1 addition & 0 deletions docs/adr/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ This log lists the architectural decisions for tuf.

- [ADR-0000](0000-use-markdown-architectural-decision-records.md) - Use Markdown Architectural Decision Records
- [ADR-0001](0001-python-version-3-6-plus.md) - Default to Python 3.6 or newer for new development
- [ADR-0003](0003-where-to-develop-TUF-1-0-0.md) - Develop TUF 1.0.0 in a subdirectory of the current TUF implementation

<!-- adrlogstop -->

Expand Down

0 comments on commit 8db81fd

Please sign in to comment.