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

Remove IsPreRelease msbuild property #72169

Merged
merged 4 commits into from
Jul 14, 2022
Merged

Remove IsPreRelease msbuild property #72169

merged 4 commits into from
Jul 14, 2022

Conversation

ViktorHofer
Copy link
Member

The property was added in dotnet/coreclr@809b8f7 years ago and isn't used anymore. Remove it to ease branding.

The property was added in dotnet/coreclr@809b8f7 years ago and isn't used anymore. Remove it to ease branding.
@ghost
Copy link

ghost commented Jul 14, 2022

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

Issue Details

The property was added in dotnet/coreclr@809b8f7 years ago and isn't used anymore. Remove it to ease branding.

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Infrastructure

Milestone: -

# If set, indicates that this is not an officially supported release
# Keep in sync with IsPrerelease in Directory.Build.props
# If set, indicates that this is not an officially supported release.
# Release branches should set this to false.
set(PRERELEASE 0)
Copy link
Member

Choose a reason for hiding this comment

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

Should this be set to 1 in main?

Copy link
Member Author

@ViktorHofer ViktorHofer Jul 14, 2022

Choose a reason for hiding this comment

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

This was recently switched to 0 by @carlossanlop in 40b3c36. I already reached out to him offline and explained that this doesn't need to be set before we actually release.

Do you think we should switch it back and make sure that it again gets changed to 0 in the release/7.0 branch?

Copy link
Member

Choose a reason for hiding this comment

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

Do you think we should switch it back and make sure that it again gets changed to 0 in the release/7.0 branch?

Yes.

If we switch it to 0 in main, we will see C/C++ compiler warnings creep in. I do not think anybody wants to sign up for fixing them once we fork for .NET 8.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed.

@ViktorHofer ViktorHofer requested a review from jkotas July 14, 2022 16:39
@ViktorHofer ViktorHofer merged commit 178553b into main Jul 14, 2022
@ViktorHofer ViktorHofer deleted the ViktorHofer-patch-1 branch July 14, 2022 23:03
@MichalStrehovsky
Copy link
Member

The property was added in dotnet/coreclr@809b8f7 years ago and isn't used anymore. Remove it to ease branding.

FWIW, it was also used by the Utf8String prototype a couple years after that and maybe others. But we do have better avenues to do this kind of things now with experimental features and runtimelab and deleting makes sense.

@ghost ghost locked as resolved and limited conversation to collaborators Aug 14, 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.

5 participants