@@ -10,7 +10,7 @@ stable 1.0.0 release scheduled for January 2022. The release *will* include:
10
10
serving as a more robust and yet more flexible stand-in replacement
11
11
for the legacy client updater
12
12
13
- As discussed in [ ADR 2] ( docs/adr/0002-pre-1-0-deprecation-strategy.md ) , this
13
+ As discussed in [ ADR 2] ( https://github.com/theupdateframework/python-tuf/blob/develop/ docs/adr/0002-pre-1-0-deprecation-strategy.md) , this
14
14
release * will not* include any legacy code, as its maintenance has become
15
15
infeasible for the python-tuf team. The pre-1.0.0 deprecation strategy from ADR
16
16
2 applies as follows:
@@ -21,7 +21,7 @@ prior to 1.0.0 will be considered, and merged (subject to normal review
21
21
processes). Note that there may be delays due to the lack of developer resources
22
22
for reviewing such pull requests.*
23
23
24
- For the reasons outlined in [ ADR 10] (docs/adr/0010-repository-library-design.md
24
+ For the reasons outlined in [ ADR 10] (https://github.com/theupdateframework/python-tuf/blob/develop/ docs/adr/0010-repository-library-design.md
25
25
), this release * will not yet* include a new * repository tool* . However, the new
26
26
* metadata API* makes it easy to replicate the desired functionality tailored to
27
27
the specific needs of any given repository (see * Migration* for details).
@@ -36,7 +36,7 @@ following migration support:
36
36
37
37
- detailed code documentation on
38
38
[ https://theupdateframework.readthedocs.io ] ( https://theupdateframework.readthedocs.io/ )
39
- - verbose [ code examples] ( examples/ ) for * client updater* usage, and
39
+ - verbose [ code examples] ( https://github.com/theupdateframework/python-tuf/tree/develop/examples ) for * client updater* usage, and
40
40
repository-side operations based on the low-level * metadata API*
41
41
- individual migration support upon
42
42
[ request] ( https://github.com/theupdateframework/python-tuf#contact )
0 commit comments