From fd802cba8b54c7c70af9826cb516d78c3c971b77 Mon Sep 17 00:00:00 2001 From: "Christopher R. Gill" Date: Fri, 15 Jan 2021 17:52:33 -0500 Subject: [PATCH 01/15] Popularity transfers doc started --- docs/nuget-org/Deprecate-packages.md | 40 ++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index efd8b6e23..d81f93d71 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -61,3 +61,43 @@ Project `My.Test.Project` has the following deprecated packages > My.Sample.Lib 6.0.0 Legacy My.Awesome.Package ``` + +## Transfer popularity to a newer package + +Package authors who have deprecated a legacy package in favor of a newer package can choose to transfer the "popularity" of the legacy to the newer package to boost the its search ranking. + +A common problem that package authors run into when they deprecate a legacy package in favor of a newer package is that the newer, less-popular package will rank lower in search results than the incumbent package for most queries. + +For example, let's say I have two packages for the same task: +* My deprecated legacy package, Contoso.Legacy with 3M downloads +* My latest package, Contoso.Latest with 100K downloads + +NuGet.org heavily considers downloads/popularity when ranking search results. Given the search query "Contoso," Contoso.Legacy will likely rank above Contoso.Latest in the results, making it more difficult for users to discover my latest package. + +To solve this problem, I can apply to transfer the popularity of my deprecated legacy package to my latest package. This would cause Contoso.Latest to rank higher in search results as if had Contoso.Legacy's 3M downloads added to its existing 100K downloads. Contoso.Legacy would rank much lower, as if it had almost all of its downloads removed. Only the internal popularity scores for the packages will be impacted, the actual download count shown for each package will not change on NuGet.org or on any client. + +> [!Note] +> Popularity transfers can make it significantly harder for consumers to find the legacy package. + +See the table below to get a concrete idea of how a popularity transfer may impact search rankings for the query "Contoso": + +| Search ranking | Before popularity transfer | After popularity transfer | +|---------------- |-------------------------------- |-------------------------------- | +| 1 | *Contoso.Legacy, 3M downloads* | *Contoso.Latest, 100K downloads* | +| 2 | Contoso.Scanner, 2M downloads | Contoso.Scanner, 2M downloads | +| 3 | Contoso.Core, 1.5M downloads | Contoso.Core, 1.5M downloads | +| 4 | Contoso.UI, 1M downloads | Contoso.UI, 1M downloads | +| ... | ... | ... | +| 20 | *Contoso.Latest, 100K downloads* | *Contoso.Legacy, 3M downloads* | + +### Popularity transfer application process + +* The legacy packages and new packages must share all owners. +* The new packages must be clearly related to the legacy packages in naming and function (i.e. an evolution or next generation). +* All versions of the legacy packages must be deprecated and point to the new packages receiving the transfer. +* The popularity transfer must not cause confusion for NuGet users or worsen the NuGet search experience. +* The new packages must have stable version. + +### Advanced popularity transfer scenarios + + From 562fee387aaf798ad0959b1d1fe3df5d6f1872e2 Mon Sep 17 00:00:00 2001 From: "Christopher R. Gill" Date: Fri, 23 Jul 2021 17:58:42 -0400 Subject: [PATCH 02/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index d81f93d71..44f701c8c 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -66,13 +66,13 @@ Project `My.Test.Project` has the following deprecated packages Package authors who have deprecated a legacy package in favor of a newer package can choose to transfer the "popularity" of the legacy to the newer package to boost the its search ranking. -A common problem that package authors run into when they deprecate a legacy package in favor of a newer package is that the newer, less-popular package will rank lower in search results than the incumbent package for most queries. +A common problem that package authors experience when they deprecate a legacy package in favor of a newer package is that the newer, less-popular package will rank lower in search results than the incumbent package for most queries. For example, let's say I have two packages for the same task: * My deprecated legacy package, Contoso.Legacy with 3M downloads * My latest package, Contoso.Latest with 100K downloads -NuGet.org heavily considers downloads/popularity when ranking search results. Given the search query "Contoso," Contoso.Legacy will likely rank above Contoso.Latest in the results, making it more difficult for users to discover my latest package. +NuGet.org heavily considers downloads/popularity when ranking search results. Given the search query "Contoso," Contoso.Legacy will likely rank above Contoso.Latest in the results, making it more difficult for users to discover. To solve this problem, I can apply to transfer the popularity of my deprecated legacy package to my latest package. This would cause Contoso.Latest to rank higher in search results as if had Contoso.Legacy's 3M downloads added to its existing 100K downloads. Contoso.Legacy would rank much lower, as if it had almost all of its downloads removed. Only the internal popularity scores for the packages will be impacted, the actual download count shown for each package will not change on NuGet.org or on any client. @@ -96,7 +96,7 @@ See the table below to get a concrete idea of how a popularity transfer may impa * The new packages must be clearly related to the legacy packages in naming and function (i.e. an evolution or next generation). * All versions of the legacy packages must be deprecated and point to the new packages receiving the transfer. * The popularity transfer must not cause confusion for NuGet users or worsen the NuGet search experience. -* The new packages must have stable version. +* The new packages must have a stable version. ### Advanced popularity transfer scenarios From 4e2a3e714a563705b0c8ab2f4bef6fb6a6acf194 Mon Sep 17 00:00:00 2001 From: "Christopher R. Gill" Date: Fri, 23 Jul 2021 18:07:50 -0400 Subject: [PATCH 03/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 44f701c8c..5b9732ea0 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -100,4 +100,6 @@ See the table below to get a concrete idea of how a popularity transfer may impa ### Advanced popularity transfer scenarios - +TODO topics: +* Transfer the popularity of several packages to a consolidated package. +* Transfer the popularity of a single package to multiple separate packages. From 38f98b8c80fc1919a3b3aeb71bb7f6410043f4e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:17:21 -0700 Subject: [PATCH 04/15] Work --- docs/nuget-org/Deprecate-packages.md | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 5b9732ea0..5766f2ff2 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -64,17 +64,16 @@ Project `My.Test.Project` has the following deprecated packages ## Transfer popularity to a newer package -Package authors who have deprecated a legacy package in favor of a newer package can choose to transfer the "popularity" of the legacy to the newer package to boost the its search ranking. +Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost its search ranking. This helps customers discover the newer package instead of the deprecated package. -A common problem that package authors experience when they deprecate a legacy package in favor of a newer package is that the newer, less-popular package will rank lower in search results than the incumbent package for most queries. +For example, let's say I have two packages: -For example, let's say I have two packages for the same task: -* My deprecated legacy package, Contoso.Legacy with 3M downloads -* My latest package, Contoso.Latest with 100K downloads +* My deprecated legacy package, `Contoso.Legacy` with 3 million downloads +* My latest package, `Contoso.Latest` with 100 thousand downloads -NuGet.org heavily considers downloads/popularity when ranking search results. Given the search query "Contoso," Contoso.Legacy will likely rank above Contoso.Latest in the results, making it more difficult for users to discover. +NuGet.org prefers search results with higher downloads/popularity. Given the search query "Contoso", my deprecated package `Contoso.Legacy` would likely rank above my latest package `Contoso.Latest` in search results. However, I'd like my customers to install `Contoso.Latest`! -To solve this problem, I can apply to transfer the popularity of my deprecated legacy package to my latest package. This would cause Contoso.Latest to rank higher in search results as if had Contoso.Legacy's 3M downloads added to its existing 100K downloads. Contoso.Legacy would rank much lower, as if it had almost all of its downloads removed. Only the internal popularity scores for the packages will be impacted, the actual download count shown for each package will not change on NuGet.org or on any client. +To solve this problem, I can apply to transfer the popularity of my deprecated legacy package to my latest package. This would cause `Contoso.Latest` to rank higher in search results, while `Contoso.Legacy` would rank lower. Only the internal popularity scores for the packages is impacted, the actual download count for each package will not be affected. > [!Note] > Popularity transfers can make it significantly harder for consumers to find the legacy package. @@ -92,14 +91,24 @@ See the table below to get a concrete idea of how a popularity transfer may impa ### Popularity transfer application process +1. Review the [popularity transfer requirements](#popularity-transfer-requirements). +2. Determine the deprecated package whose popularity should be transferred. Determine the stable package(s) that should receive the popularity transfer. package you would like to transfer which deprecated packages you would like + +After the application is submitted, we will notify you of your application's acceptance or rejection (with the criteria that caused rejection). We may need to ask additional identifying questions to confirm owner identity. + +#### Popularity transfer requirements + * The legacy packages and new packages must share all owners. * The new packages must be clearly related to the legacy packages in naming and function (i.e. an evolution or next generation). * All versions of the legacy packages must be deprecated and point to the new packages receiving the transfer. * The popularity transfer must not cause confusion for NuGet users or worsen the NuGet search experience. * The new packages must have a stable version. +* The legacy package must have fewer than 5 new packages. +* The legacy package must not receive popularity transfers from another deprecated package. ### Advanced popularity transfer scenarios TODO topics: * Transfer the popularity of several packages to a consolidated package. * Transfer the popularity of a single package to multiple separate packages. +* Daisy chaining From ed2282ec638516555b792c10d5b0b2341ea2887e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:37:07 -0700 Subject: [PATCH 05/15] Add advanced scenarios --- docs/nuget-org/Deprecate-packages.md | 44 +++++++++++++++++++++++----- 1 file changed, 37 insertions(+), 7 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 5766f2ff2..e2517deed 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -69,7 +69,7 @@ Package authors who have deprecated a legacy package can choose to transfer its For example, let's say I have two packages: * My deprecated legacy package, `Contoso.Legacy` with 3 million downloads -* My latest package, `Contoso.Latest` with 100 thousand downloads +* My latest package, `Contoso.Latest` with 5 downloads NuGet.org prefers search results with higher downloads/popularity. Given the search query "Contoso", my deprecated package `Contoso.Legacy` would likely rank above my latest package `Contoso.Latest` in search results. However, I'd like my customers to install `Contoso.Latest`! @@ -82,12 +82,12 @@ See the table below to get a concrete idea of how a popularity transfer may impa | Search ranking | Before popularity transfer | After popularity transfer | |---------------- |-------------------------------- |-------------------------------- | -| 1 | *Contoso.Legacy, 3M downloads* | *Contoso.Latest, 100K downloads* | +| 1 | *Contoso.Legacy, 3M downloads* | *Contoso.Latest, 5 downloads* | | 2 | Contoso.Scanner, 2M downloads | Contoso.Scanner, 2M downloads | | 3 | Contoso.Core, 1.5M downloads | Contoso.Core, 1.5M downloads | | 4 | Contoso.UI, 1M downloads | Contoso.UI, 1M downloads | | ... | ... | ... | -| 20 | *Contoso.Latest, 100K downloads* | *Contoso.Legacy, 3M downloads* | +| 20 | *Contoso.Latest, 5 downloads* | *Contoso.Legacy, 3M downloads* | ### Popularity transfer application process @@ -108,7 +108,37 @@ After the application is submitted, we will notify you of your application's acc ### Advanced popularity transfer scenarios -TODO topics: -* Transfer the popularity of several packages to a consolidated package. -* Transfer the popularity of a single package to multiple separate packages. -* Daisy chaining +### Package consolidations + +I can transfer the popularity of multiple deprecated packages in favor of a single new package. For example, let's say I have 3 packages: + +* My first deprecated legacy package, `Contoso.Legacy1` +* My second deprecated legacy package, `Contoso.Legacy2` +* My new consolidated package, `Contoso.Latest` + +After I deprecate `Contoso.Legacy1` and `Contoso.Legacy2`, I can apply to transfer their popularity to `Contoso.Latest`. + +### Package splits + +If a package is deprecated in favor of multiple new packages, its popularity can be transferred to up to 5 packages. For example, let's say I have 3 packages: + +* My deprecated legacy package, `Contoso.Legacy` +* My first new package, `Contoso.Web` +* My second new package, `Contoso.Cloud` + +After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `Contoso.Web` and `Contoso.Cloud`. + +> [!Note] +> The popularity will be split evenly between all new packages. The new packages will not be as popular as the deprecated package in search rankings. As a result, we recommend transferring your deprecated package's popularity to just a single package if possible. + +Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost its search ranking + +### Popularity transfer chains + +A package that is receiving popularity may not transfer its own popularity to another package. For example, say I have 3 packages: + +* My deprecated legacy package, `Contoso.First` +* My deprecated legacy package, `Contoso.Second` +* My new package, `Contoso.Latest` + +If `Contoso.First` transfers its popularity to `Contoso.Second,` then `Contoso.Second` cannot transfer its popularity to `Contoso.Latest`. Instead, we recommend transferring the popularity of both `Contoso.First` and `Contoso.Second` to `Contoso.Latest`, as per the [Package consolidations](#package-consolidations) scenario. From 8d4d3ec775142e86a45e6280f1f95c2ae699b288 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:44:58 -0700 Subject: [PATCH 06/15] Tweaks --- docs/nuget-org/Deprecate-packages.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index e2517deed..1e2f13468 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -64,14 +64,14 @@ Project `My.Test.Project` has the following deprecated packages ## Transfer popularity to a newer package -Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost its search ranking. This helps customers discover the newer package instead of the deprecated package. +Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost the newer package's search ranking. This helps customers discover the newer package instead of the deprecated package. For example, let's say I have two packages: * My deprecated legacy package, `Contoso.Legacy` with 3 million downloads * My latest package, `Contoso.Latest` with 5 downloads -NuGet.org prefers search results with higher downloads/popularity. Given the search query "Contoso", my deprecated package `Contoso.Legacy` would likely rank above my latest package `Contoso.Latest` in search results. However, I'd like my customers to install `Contoso.Latest`! +NuGet.org prefers search results with higher downloads/popularity. Given the search query "Contoso", my deprecated package `Contoso.Legacy` would likely rank above my latest package `Contoso.Latest` in search results. To solve this problem, I can apply to transfer the popularity of my deprecated legacy package to my latest package. This would cause `Contoso.Latest` to rank higher in search results, while `Contoso.Legacy` would rank lower. Only the internal popularity scores for the packages is impacted, the actual download count for each package will not be affected. @@ -92,7 +92,8 @@ See the table below to get a concrete idea of how a popularity transfer may impa ### Popularity transfer application process 1. Review the [popularity transfer requirements](#popularity-transfer-requirements). -2. Determine the deprecated package whose popularity should be transferred. Determine the stable package(s) that should receive the popularity transfer. package you would like to transfer which deprecated packages you would like +2. Determine the deprecated package whose popularity should be transferred, and, the stable package(s) that should receive the popularity transfer. +3. Email account@nuget.org with the package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. After the application is submitted, we will notify you of your application's acceptance or rejection (with the criteria that caused rejection). We may need to ask additional identifying questions to confirm owner identity. @@ -108,7 +109,7 @@ After the application is submitted, we will notify you of your application's acc ### Advanced popularity transfer scenarios -### Package consolidations +#### Package consolidations I can transfer the popularity of multiple deprecated packages in favor of a single new package. For example, let's say I have 3 packages: @@ -118,7 +119,7 @@ I can transfer the popularity of multiple deprecated packages in favor of a sing After I deprecate `Contoso.Legacy1` and `Contoso.Legacy2`, I can apply to transfer their popularity to `Contoso.Latest`. -### Package splits +#### Package splits If a package is deprecated in favor of multiple new packages, its popularity can be transferred to up to 5 packages. For example, let's say I have 3 packages: @@ -133,7 +134,7 @@ After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `C Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost its search ranking -### Popularity transfer chains +#### Popularity transfer chains A package that is receiving popularity may not transfer its own popularity to another package. For example, say I have 3 packages: From e22877fe8cfbe2290481683864a769aaf20d7485 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:46:41 -0700 Subject: [PATCH 07/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 1e2f13468..b59e69bf3 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -132,8 +132,6 @@ After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `C > [!Note] > The popularity will be split evenly between all new packages. The new packages will not be as popular as the deprecated package in search rankings. As a result, we recommend transferring your deprecated package's popularity to just a single package if possible. -Package authors who have deprecated a legacy package can choose to transfer its "popularity" to a newer package to boost its search ranking - #### Popularity transfer chains A package that is receiving popularity may not transfer its own popularity to another package. For example, say I have 3 packages: From 3e4b8a89db2fd3091950ba88570a2fc4157a656a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:49:23 -0700 Subject: [PATCH 08/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index b59e69bf3..7c3ca9da6 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -121,7 +121,7 @@ After I deprecate `Contoso.Legacy1` and `Contoso.Legacy2`, I can apply to transf #### Package splits -If a package is deprecated in favor of multiple new packages, its popularity can be transferred to up to 5 packages. For example, let's say I have 3 packages: +A deprecated package's popularity can be transferred to up to 5 packages. This is useful if a package is deprecated of multiple new packages. For example, let's say I have 3 packages: * My deprecated legacy package, `Contoso.Legacy` * My first new package, `Contoso.Web` @@ -134,7 +134,7 @@ After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `C #### Popularity transfer chains -A package that is receiving popularity may not transfer its own popularity to another package. For example, say I have 3 packages: +A deprecated package cannot transfer its popularity if it is already receiving popularity from another deprecated package. For example, say I have 3 packages: * My deprecated legacy package, `Contoso.First` * My deprecated legacy package, `Contoso.Second` From 71bfb2bb3c644004da7613b483efea0510b0387b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 16:58:18 -0700 Subject: [PATCH 09/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 7c3ca9da6..f583c5241 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -129,8 +129,8 @@ A deprecated package's popularity can be transferred to up to 5 packages. This i After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `Contoso.Web` and `Contoso.Cloud`. -> [!Note] -> The popularity will be split evenly between all new packages. The new packages will not be as popular as the deprecated package in search rankings. As a result, we recommend transferring your deprecated package's popularity to just a single package if possible. +> [!Warning] +> The transferred popularity will be split evenly between all new packages. As a result, we recommend transferring your deprecated package's popularity to as few packages as possible. #### Popularity transfer chains From 6436087d46cc97c55a554e9e2ec660bae215cee3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 17:02:51 -0700 Subject: [PATCH 10/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index f583c5241..fe5da4594 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -93,7 +93,7 @@ See the table below to get a concrete idea of how a popularity transfer may impa 1. Review the [popularity transfer requirements](#popularity-transfer-requirements). 2. Determine the deprecated package whose popularity should be transferred, and, the stable package(s) that should receive the popularity transfer. -3. Email account@nuget.org with the package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. +3. Email [account@nuget.org](mailto:account@nuget.org) with the package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. After the application is submitted, we will notify you of your application's acceptance or rejection (with the criteria that caused rejection). We may need to ask additional identifying questions to confirm owner identity. From 6878bb790647ffef826d845e48d253ec4fdf4ed5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 17:03:33 -0700 Subject: [PATCH 11/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index fe5da4594..32196c253 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -93,7 +93,7 @@ See the table below to get a concrete idea of how a popularity transfer may impa 1. Review the [popularity transfer requirements](#popularity-transfer-requirements). 2. Determine the deprecated package whose popularity should be transferred, and, the stable package(s) that should receive the popularity transfer. -3. Email [account@nuget.org](mailto:account@nuget.org) with the package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. +3. Email [account@nuget.org](mailto:account@nuget.org) with the deprecated package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. After the application is submitted, we will notify you of your application's acceptance or rejection (with the criteria that caused rejection). We may need to ask additional identifying questions to confirm owner identity. From 22d0b8bab52fdfc7bfb7d920c0c785ad0e7dcecb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Fri, 23 Jul 2021 17:04:24 -0700 Subject: [PATCH 12/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 32196c253..305a48818 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -92,8 +92,7 @@ See the table below to get a concrete idea of how a popularity transfer may impa ### Popularity transfer application process 1. Review the [popularity transfer requirements](#popularity-transfer-requirements). -2. Determine the deprecated package whose popularity should be transferred, and, the stable package(s) that should receive the popularity transfer. -3. Email [account@nuget.org](mailto:account@nuget.org) with the deprecated package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. +2. Email [account@nuget.org](mailto:account@nuget.org) with the deprecated package whose popularity should be transferred, and, the list of stable package(s) that should receive the popularity transfer. After the application is submitted, we will notify you of your application's acceptance or rejection (with the criteria that caused rejection). We may need to ask additional identifying questions to confirm owner identity. From 310a715544ed8e47d23efb21a1f5aaf6fed8b656 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Tue, 27 Jul 2021 11:37:46 -0700 Subject: [PATCH 13/15] Update docs/nuget-org/Deprecate-packages.md Co-authored-by: Christopher R. Gill --- docs/nuget-org/Deprecate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 305a48818..047648063 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -120,7 +120,7 @@ After I deprecate `Contoso.Legacy1` and `Contoso.Legacy2`, I can apply to transf #### Package splits -A deprecated package's popularity can be transferred to up to 5 packages. This is useful if a package is deprecated of multiple new packages. For example, let's say I have 3 packages: +A deprecated package's popularity can be transferred to, and divided among, up to 5 newer packages. This is useful if the functionality of a deprecated package has been split among multiple new packages. For example, let's say I have 3 packages: * My deprecated legacy package, `Contoso.Legacy` * My first new package, `Contoso.Web` From ec0fd1adfe66ca0d104aee96601cdb3edb830e4f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Tue, 27 Jul 2021 11:38:23 -0700 Subject: [PATCH 14/15] Update docs/nuget-org/Deprecate-packages.md Co-authored-by: Christopher R. Gill --- docs/nuget-org/Deprecate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index 047648063..cc6c6907f 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -126,7 +126,7 @@ A deprecated package's popularity can be transferred to, and divided among, up t * My first new package, `Contoso.Web` * My second new package, `Contoso.Cloud` -After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to `Contoso.Web` and `Contoso.Cloud`. +`Contoso.Legacy` includes both web and cloud functionality, but I decided to separate that functionality into different packages for the next generation. After I deprecate `Contoso.Legacy`, I can apply to transfer its popularity to both `Contoso.Web` and `Contoso.Cloud`. > [!Warning] > The transferred popularity will be split evenly between all new packages. As a result, we recommend transferring your deprecated package's popularity to as few packages as possible. From b6ff4f4f3ff7d4b4b603efa722291a2922d073c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Sharma?= <737941+loic-sharma@users.noreply.github.com> Date: Tue, 27 Jul 2021 11:39:50 -0700 Subject: [PATCH 15/15] Update Deprecate-packages.md --- docs/nuget-org/Deprecate-packages.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/nuget-org/Deprecate-packages.md b/docs/nuget-org/Deprecate-packages.md index cc6c6907f..c9189ce99 100644 --- a/docs/nuget-org/Deprecate-packages.md +++ b/docs/nuget-org/Deprecate-packages.md @@ -103,7 +103,6 @@ After the application is submitted, we will notify you of your application's acc * All versions of the legacy packages must be deprecated and point to the new packages receiving the transfer. * The popularity transfer must not cause confusion for NuGet users or worsen the NuGet search experience. * The new packages must have a stable version. -* The legacy package must have fewer than 5 new packages. * The legacy package must not receive popularity transfers from another deprecated package. ### Advanced popularity transfer scenarios