Change the version-less package page to show the latest stable, while giving users a good indication that there's a pre-release version available

[half-ogre]

This is to avoid confusion for someone just coming to the landing page of a package expecting to get the latest. They should be shown the latest stable, not a pre-release package. At the same time, we want to make it easy for users to see and try out pre-release packages, so we want to make it that very easy to discover.

[markheath]

+1, I would like this feature.

[jeffhandley]

+3 (@howarddierking, @RanjiniM, and me). Also, search results should always be versionless when we have this in place. For instance, presently, searching for "nuget.core" returns a "NuGet.Core 2.0.1" result instead of just "NuGet.Core."

[analogrelay]

The client focuses on stable versions, so this seems good.

[analogrelay]

Postponing to the site redesign.

[TimLovellSmith]

Given that we said this is P1 why are we postponing it? I'm pulling this into this milestone.

[TimLovellSmith]

How the fix will need to work:
We use the wonderful FindPackageByIdAndVersion method to find packages whenever someone doesn't specify a version. We actuallyuse that function from all these places where it seems logical to make the same change for consistency:

1. API calls (e.g. nuget.exe) for:
   a) verify package key
   b) delete package [unlist]
   c) public package [relist]
   d) get package [download, including part of package install/restore etc.]
2. PackagesController
   a) display package
   b) report abuse
   c) contact support
   d) edit package
   e) set license report visibility
   f) undo pending edits

The possibly most risky change to make is changing the API for get package. However I don't think it's risky in practice, because in practice nobody is calling the API without a version which they have looked up in the package feed.

[If they were, they might not have intended to get a prerelease package anyway, so yes this is probably a good change...]

[TimLovellSmith]

It turns out that API call for get package already was passing a special parameter so that it would never let you get a prerelease version without specifying the version.