Skip to content

Keep Blazor at pre-release for 3.1 #16829

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

Merged
merged 1 commit into from
Nov 13, 2019
Merged

Conversation

JunTaoLuo
Copy link
Contributor

This ensures that the following Blazor packages remain branded as 3.1.x-preview4:
• Microsoft.AspNetCore.Blazor
• Microsoft.AspNetCore.Blazor.HttpClient
• Microsoft.AspNetCore.Blazor.DataAnnotations.Validation
• Microsoft.AspNetCore.Blazor.Templates
• Microsoft.AspNetCore.Blazor.Build
• Microsoft.AspNetCore.Blazor.Mono
• Microsoft.AspNetCore.Blazor.Server
• Microsoft.AspNetCore.Blazor.DevServer

Note that Microsoft.AspNetCore.Blazor.Mono is built in aspnet/Blazor so that will require a different branding change.

@JunTaoLuo JunTaoLuo added the area-blazor Includes: Blazor, Razor Components label Nov 4, 2019
@JunTaoLuo JunTaoLuo added this to the 3.1.0 milestone Nov 4, 2019
@@ -19,6 +19,9 @@
<IncludePreReleaseLabelInPackageVersion Condition=" '$(DotNetFinalVersionKind)' == 'release' ">false</IncludePreReleaseLabelInPackageVersion>
<PreReleaseVersionLabel>preview$(PreReleasePreviewNumber)</PreReleaseVersionLabel>
<PreReleaseBrandingLabel>Preview $(PreReleasePreviewNumber)</PreReleaseBrandingLabel>
<!-- Blazor Client packages will not RTM with 3.1 -->
<BlazorClientPreReleasePreviewNumber>4</BlazorClientPreReleasePreviewNumber>
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
<BlazorClientPreReleasePreviewNumber>4</BlazorClientPreReleasePreviewNumber>
<BlazorClientPreReleasePreviewNumber>3</BlazorClientPreReleasePreviewNumber>

Don't jump ahead of $(PreReleasePreviewNumber). We can change this when stabilizing versions and removing the other property.

@JunTaoLuo
Copy link
Contributor Author

Yea this shouldn't be merged until we have branding updates for GA.

@wtgodbe
Copy link
Member

wtgodbe commented Nov 8, 2019

I'll merge this when I update branding to stable Sunday/Monday

@JunTaoLuo
Copy link
Contributor Author

@wtgodbe are these ready to go in yet?

@wtgodbe wtgodbe merged commit 19ca6e9 into release/3.1 Nov 13, 2019
@wtgodbe wtgodbe deleted the johluo/blazor-prerelease branch November 13, 2019 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants