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.

Sign up for GitHub

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

Jump to bottom

[10.0] Target loc back to main after we're done with 9.0 #95024

Closed
carlossanlop opened this issue Nov 20, 2023 · 5 comments · Fixed by #111872
Closed

[10.0] Target loc back to main after we're done with 9.0 #95024

carlossanlop opened this issue Nov 20, 2023 · 5 comments · Fixed by #111872
Assignees
@carlossanlop
Labels
area-Infrastructure-libraries in-pr There is an active PR which will close this issue when it is merged
Milestone
10.0.0

Comments

@carlossanlop
Copy link
Member

We should do this right after we snap rc1.

Basically do what we did in 8.0: #90812

And then revert it after we ship 9.0 like we did here:
#95014
@carlossanlop carlossanlop added this to the 9.0.0 milestone Nov 20, 2023
@ghost
Copy link

ghost commented Nov 20, 2023

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

Issue Details

We should do this right after we snap rc1.

Basically do what we did in 8.0: #90812

And then revert it after we ship 9.0 like we did here:
#95014

Author: carlossanlop
Assignees: -
Labels:

area-Infrastructure-libraries, blocking-release
Milestone: 9.0.0

@akoeplinger
Copy link
Member

I don't think we need to follow #90812 exactly since we (hopefully) don't need to disable OneLoc on main.

The only change needed should be setting MirrorBranch: release/9.0 in the release/9.0 branch.

@ericstj
Copy link
Member

ericstj commented Sep 4, 2024

Ping @carlossanlop - I think you did this?

@carlossanlop
Copy link
Member Author

Yep, this is done. We're getting the Loc PRs created to the release/9.0 branch: #106995

Let's keep this open so that we remember to restore the Loc branch to main after we release.

@ericstj
Copy link
Member

ericstj commented Sep 17, 2024

Ok, since this is tracking work post-release I'll move to the 10.0.0 milestone.

@ericstj ericstj modified the milestones: 9.0.0, 10.0.0 Sep 17, 2024
@ericstj ericstj changed the title [9.0] Temporarily target loc to the release/9.0 branch [10.0] Target loc back to main after we're done with 9.0 Sep 17, 2024
@akoeplinger akoeplinger mentioned this issue Dec 20, 2024
Closed
@carlossanlop carlossanlop mentioned this issue Jan 27, 2025
Merged
@dotnet-policy-service dotnet-policy-service bot added the in-pr There is an active PR which will close this issue when it is merged label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carlossanlop carlossanlop

Labels
area-Infrastructure-libraries in-pr There is an active PR which will close this issue when it is merged
Projects
None yet
Milestone
10.0.0
Development

Successfully merging a pull request may close this issue.

Switch OneLoc back to main carlossanlop/runtime
3 participants
@carlossanlop @akoeplinger @ericstj