Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Arcade version suffixes for local (3.0.0-dev) and PR builds (3.0.0-ci) #10279

Merged
merged 7 commits into from
May 16, 2019

Conversation

natemcmaster
Copy link
Contributor

Part of #7280 (Convert to Arcade)

This updates our versioning to better match Arcades https://github.com/dotnet/arcade/blob/master/Documentation/CorePackages/Versioning.md

Effective changes

  • Local builds will build and produce packages as 3.0.0-dev
  • PR builds will build and produce packages as 3.0.0-ci

Everything else should remain the same

@@ -40,15 +40,17 @@
<BuildNumberSuffix>$(_BuildNumberShortDate)-$(VersionSuffixBuildOfTheDayPadded)</BuildNumberSuffix>

<FileRevisionVersion>$(_BuildNumberShortDate)</FileRevisionVersion>
<VersionSuffix>$(PreReleaseLabel)-$(BuildNumberSuffix)</VersionSuffix>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would changing the dash to a period resolve the format difference in releases between AspNetCoreRuntime.3.0.x64.3.0.0-preview-19081-0488 and Microsoft.Extensions.Logging.3.0.0-preview5.19227.9 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it would resolve the format difference, but it would create more problems. See #4339

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That issue was written before we moved to include the preview number in our versions. So, we could make the switch when we next update the branding in this repo. Suggest reopening #4339.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re opened. I'll bring it up during our area-platform triage. It's not really a build team decision to do this or not because this impacts the appearance and behavior of the product, so I won't attempt to address that in this PR.

@Eilon Eilon added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label May 16, 2019
@natemcmaster natemcmaster changed the title Match Arcade versioning (Local builds = 3.0.0-dev, PR builds = 3.0.0-ci) Use Arcade version suffixes for local (3.0.0-dev) and PR builds (3.0.0-ci) May 16, 2019
@natemcmaster natemcmaster merged commit 117dd8c into dotnet:master May 16, 2019
@natemcmaster natemcmaster deleted the versioning branch May 16, 2019 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants