The artifacts/packages/$(Configuration) directory will now look like the following (subset):

• Release
  • Microsoft.DotNet.Try.Markdown.1.0.0.nupkg
• Shipping
  • dotnet-try.1.0.19462.0.nupkg
  • Microsoft.DotNet.Try.Markdown.1.0.0-beta.19462.0.nupkg

With this, the dotnet-try package always has a date-stamped version. This is unchanged from what we had before.

The real change is that other packages (e.g., Microsoft.DotNet.Try.Markdown) will produce both a 1.0.0 and 1.0.0-beta.<timestamp> version, which means we can publish the *-beta.* packages as appropriate and when we decide we want to promote one of those to release, we simply upload the corresponding 1.0.0 package from the Release directory.

The only caveat is that once we've shipped a Release version of a package, we'll need to increment the 1.0.0 version to 1.0.1, 1.0.2, etc. When it comes to that, however, the dotnet-try package will be insulated and will continue to produce 1.0.<datestamp>.<buildNumber>.