-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Update Versions.props for Dev18 #77138
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
Conversation
dibarbet
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're creating a dev18 branch, IMHO we should do some kind of merge from main to it. Otherwise it will get out of date quickly. And it is different from servicing branches in that it should be up to date with main (even infra).
Probably the easiest way would be to utilize arcade's branch merge github action. We would configure it to merge main to the dev18 branch maybe once a day or once a week.
Similar to https://github.com/dotnet/vscode-csharp/blob/main/.github/workflows/branch-merge.yml , except with a scheduled trigger instead of on push
eng/config/PublishData.json
Outdated
| "Shipping", | ||
| "NonShipping" | ||
| ], | ||
| "vsBranch": "dev/monicaro/versioning", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this is temporary until we get an actual branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct, that's in progress
eng/config/PublishData.json
Outdated
| "insertionTitlePrefix": "[d17.14 P1]", | ||
| "insertionCreateDraftPR": false | ||
| }, | ||
| "release/dev18.0": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(spoke offline) - this change needs to be made in main
The Arcade inter-branch merge GH action creates merge commits with a differently formatted message (ex. `[automated] Merge branch 'prerelease' => 'main' (#8039)`) Tested by generating PR list between Roslyn main and Roslyn release/dev18.0: *Before*: ```md ### Changes from [main](dotnet/roslyn@main) to [release/dev18.0](dotnet/roslyn@release/dev18.0): [View Complete Diff of Changes](https://github.com/dotnet/roslyn/compare/main...release/dev18.0?w=1) - [[automated] Merge branch 'main' => 'release/dev18.0' (77445)](dotnet/roslyn#77445) - [[automated] Merge branch 'main' => 'release/dev18.0' (77441)](dotnet/roslyn#77441) - [[automated] Merge branch 'main' => 'release/dev18.0' (77431)](dotnet/roslyn#77431) - [[automated] Merge branch 'main' => 'release/dev18.0' (77409)](dotnet/roslyn#77409) - [[automated] Merge branch 'main' => 'release/dev18.0' (77374)](dotnet/roslyn#77374) - [[automated] Merge branch 'main' => 'release/dev18.0' (77292)](dotnet/roslyn#77292) - [[automated] Merge branch 'main' => 'release/dev18.0' (77226)](dotnet/roslyn#77226) - [[automated] Merge branch 'main' => 'release/dev18.0' (77153)](dotnet/roslyn#77153) - [Update Versions.props for Dev18 (77138)](dotnet/roslyn#77138) ``` *After*: ```md ### Changes from [main](dotnet/roslyn@main) to [release/dev18.0](dotnet/roslyn@release/dev18.0): [View Complete Diff of Changes](https://github.com/dotnet/roslyn/compare/main...release/dev18.0?w=1) - [Update Versions.props for Dev18 (77138)](dotnet/roslyn#77138) ```
No description provided.