Skip to content
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

Roadmap for PEP 458 #10672

Open
38 of 52 tasks
di opened this issue Feb 1, 2022 · 6 comments
Open
38 of 52 tasks

Roadmap for PEP 458 #10672

di opened this issue Feb 1, 2022 · 6 comments
Labels
meta Meta issues (rollouts, etc)

Comments

@di
Copy link
Member

di commented Feb 1, 2022

This is a meta-issue to document the roadmap for PyPI's support for PEP 458. This top-level comment will be updated as the roadmap progresses. Comments on this issue should be limited to a discussion of this roadmap only, e.g. whether there are steps missing, discovered to be necessary or resolved.

Roadmap

Downstream issues unblocked once this roadmap is complete:


This is likely incomplete, cc @ewdurbin @woodruffw @trishankatdatadog @JustinCappos @mnm678 @joshuagl @jku @pradyunsg @brainwane for your input & awareness.

@di di added the meta Meta issues (rollouts, etc) label Feb 1, 2022
@di
Copy link
Member Author

di commented Feb 1, 2022

(Sorry, cc @kairoaraujo as well!)

@di
Copy link
Member Author

di commented Feb 2, 2022

#8586 has been merged, next step on our end here is setting up the CDN to serve the hashed pages from storage.

@di
Copy link
Member Author

di commented Feb 22, 2022

tuf==1.0.0 has been released: https://pypi.org/project/tuf/1.0.0/

kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Mar 4, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Mar 30, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Mar 31, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Apr 11, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue May 30, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
@brainwane
Copy link
Contributor

I may be mistaken, but it looks like movement on PEP 458 has slowed -- what can we do to help get it moving again? Should I be watching https://github.com/jku/repository-playground or helping test #10870 or #8955 or #7488? Thanks!

@ofek
Copy link
Contributor

ofek commented Jun 25, 2022

Please let me know if I can help.

kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Jun 25, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
@kairoaraujo
Copy link
Contributor

Hi, @brainwane and @ofek.
Helping to review and test PR #10870 for the TUF initialization for development would be great. 🙂

kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Aug 22, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Sep 20, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
kairoaraujo pushed a commit to kairoaraujo/warehouse that referenced this issue Sep 30, 2022
This work refactors the
[Draft PR](pypi#7488) by
@ woodruffw, to build a new repository tool on top of the Python-TUF
Metadata API, and use it instead of the Python-TUF repository tool
that was deprecated in v1.0.0.

Part of pypi#10672

Signed-off-by: Kairo de Araujo <kdearaujo@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Meta issues (rollouts, etc)
Projects
None yet
Development

No branches or pull requests

4 participants