They are indeed the same thing as Mohamed suggests. Disappointingly, NuGet (still) offers no formal mechanism for distinguishing pre-release "use at your own risk" packages from released "expect to be stable/reliable" packages and so teams are stuck following often discordant and poorly documented conventions for versioning to convey this information.
FWIW, the more people that raise (and vote for) the NuGet team resolving this process shortcoming in the NuGet ecosystem, the more likely that they will consider acting to address it so we'd encourage you (and others!) to visit http://nuget.codeplex.com and submit/vote/escalate this issue. -Steve B. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/J5mNm470gToJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
