Skip to content

Conversation

@carlossanlop
Copy link
Contributor

Do not merge. This depends on snapping first.

This PR is loosely based on what we did last year: https://github.com/dotnet/runtime/pull/57095/files

I suspect this change is incomplete, since many of the elements modified in last year's PR do not exist today.

@ghost
Copy link

ghost commented Aug 16, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Do not merge. This depends on snapping first.

This PR is loosely based on what we did last year: https://github.com/dotnet/runtime/pull/57095/files

I suspect this change is incomplete, since many of the elements modified in last year's PR do not exist today.

Author: carlossanlop
Assignees: carlossanlop
Labels:

area-Infrastructure

Milestone: 8.0.0

<!-- Set assembly version to align with major and minor version,
as for the patches and revisions should be manually updated per assembly if it is serviced. -->
<AssemblyVersion>$(MajorVersion).$(MinorVersion).0.0</AssemblyVersion>
<AssemblyVersion>$(PreviousReleaseMajorVersion).$(MinorVersion).0.0</AssemblyVersion>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<AssemblyVersion>$(PreviousReleaseMajorVersion).$(MinorVersion).0.0</AssemblyVersion>
<AssemblyVersion>7.$(MinorVersion).0.0</AssemblyVersion>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll apply your suggestion, but can you please explain why this value can't stay in $(MajorVersion)? Why do we need to use 7 instead of 8?

Copy link
Member

Choose a reason for hiding this comment

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

In the past release when we branded main to .NET 7 we didn't bump the assembly versions as part of the branding update. We only incremented the package major version to avoid bin clashes when packages being uploaded to the same feed.

Incrementing the assembly versions should happen afterwards to not block this PR: I assume that the assembly update could cause other issues that would need to be resolved.

@carlossanlop carlossanlop changed the title [Draft] Bump main branding to 8.0 Bump main branding to 8.0 Aug 16, 2022
@carlossanlop carlossanlop marked this pull request as ready for review August 16, 2022 19:39
@carlossanlop
Copy link
Contributor Author

@ViktorHofer any chance you can give a quick look at last year's PR and let me know if I missed anything? https://github.com/dotnet/runtime/pull/57095/files

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

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

LGTM. Unsure if the SdkBandVersion needs to be incremented as well, but that can probably be done in a follow-up.

@carlossanlop
Copy link
Contributor Author

Ci failures unrelated.

@carlossanlop carlossanlop merged commit 3142a06 into dotnet:main Aug 17, 2022
@carlossanlop carlossanlop deleted the HereComesNET8 branch August 17, 2022 01:34
@ghost ghost locked as resolved and limited conversation to collaborators Sep 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants