-
Notifications
You must be signed in to change notification settings - Fork 956
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
Consolidate pypi.org migration notes #401
Comments
I'm going to handle this now, as we need to add info about user registration being turned off in legacy PyPI as a result of https://status.python.org/incidents/mgjw1g5yjy5j |
- continue to describe the migration on the recommendations page, but link to the migration page for details - merge the info from the recommendations page into the migration page - add a new section about user registration migrating due to a spam attack against the legacy service
#401 handles the consolidation, and also adds the note about user registration migrating. |
- continue to describe the migration on the recommendations page, but link to the migration page for details - merge the info from the recommendations page into the migration page - add a new section about user registration migrating due to a spam attack against the legacy service
I missed the chance to review #436 before it was merged. Thanks for it, @ncoghlan. As of earlier this week we do have package and release management features in Warehouse so I'll update the "Managing published packages and releases" section with a new PR shortly. |
Advise users on package, release management features
We currently have two sets of pypi.org migration notes:
Aside from duplicating information, the first set also kind of overwhelms that tool recommendation lists that are intended to be the main purpose of that particular guide.
It would be preferable to consolidate all the actual migration notes into the migration guide, and update the section on the tool recommendations page to just link to the migration guide.
The text was updated successfully, but these errors were encountered: