From 96be626c87c3ca325b18aa6653602f5e7087497f Mon Sep 17 00:00:00 2001 From: Nate McMaster Date: Fri, 5 Oct 2018 12:09:55 -0700 Subject: [PATCH] Update branding to 2.1.6-servicing (#289) Per discussion with our team, we want to make the following changes to versioning during servicing updates: * The versioning on packages with ship with ASP.NET Core should be consistent * (No change) on packages with changes in them ship during servicing updates * Version gaps are okay. For example, this repo is producing a patch for 2.1.6, so packages will be 2.1.6. It did not patch for 2.1.4 or 2.1.3 so those versions will be skipped. This also includes another minor change: for consistency with the rest of the .NET Core teams, pre-release servicing builds will be 2.1.x-servicing-buildnumber. --- version.props | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/version.props b/version.props index 16607eed0f..a60480f5bf 100644 --- a/version.props +++ b/version.props @@ -1,9 +1,9 @@  - 2.1.5 - rtm - $(VersionPrefix) - $(VersionPrefix)-$(VersionSuffix)-final + 2.1.6 + servicing + $(VersionPrefix) + $(VersionPrefix)-$(VersionSuffix)-final t000 a- $(FeatureBranchVersionPrefix)$(VersionSuffix)-$([System.Text.RegularExpressions.Regex]::Replace('$(FeatureBranchVersionSuffix)', '[^\w-]', '-'))