-
Notifications
You must be signed in to change notification settings - Fork 644
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
[Package Renames] Document how to apply for popularity transfers #7943
Milestone
Comments
This was referenced Apr 13, 2020
loic-sharma
changed the title
[Package Renames] Add documentation
[Package Renames] Add documentation on how to apply for popularity transfers
Jul 2, 2020
loic-sharma
changed the title
[Package Renames] Add documentation on how to apply for popularity transfers
[Package Renames] Document how to apply for popularity transfers
Jul 2, 2020
Documentation is written and approved but we are blocking until PMs decide:
|
loic-sharma
added a commit
to NuGet/docs.microsoft.com-nuget
that referenced
this issue
Aug 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of the package renames epic (#7896), we created a feature that lets authors transfer the popularity of packages. This would let authors make the replacement package discoverable in search results even if the renamed package is popular. For example, the package
FAKE
was replaced byfake-cli
, however,FAKE
is still the top result for the "fake" search query.Originally, the plan was to add UI to let authors customize their popularity transfers. Due to concerns that misusing this advanced feature could hurt nuget.org's search results, we've decided to that popularity transfers should be reviewed by the nuget.org team. Customers will apply for popularity transfers using a process similar to our Package Id prefix reservation process.
/cc @chgill-MSFT
The text was updated successfully, but these errors were encountered: