Commented Unassigned: Support for SemVer 2.0 specification's notion of pre-release builds [3416]

SemVer 2.0 was just released, [as announced by Phil Haack](http://haacked.com/archive/2013/06/18/semver-2-0-released.aspx), and the major feature is the addition of a specification for build numbers for pre-release packages. It would be great to see NuGet add support for both understanding this from a package building as well as package discovery from feeds.
Comments: Yes, thanks. We have been working very closely with Phil on getting SemVer 2.0 to reach RTM. We do still have some important questions to ask, so I'm glad you filed this issue. While I think we can all agree that "Support build numbers" is an important feature request (and I think we have duplicates in the issue list already), we need to understand details of what that actually means. 1. Can you provide scenarios that you would like to be supported? 1. Should nuget.org support build numbers in packages? 1. What behaviors do you expect from NuGet in the VS dialog and PowerShell consoles for handling build numbers? We understand that the general concept of build number support is important to a lot of people, but before we start adding that support, we need to understand better what scenarios this targets and how it should behave. Thanks!