You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5. Set the new branch to receive auto-merges from `main`, and also set the old release branch to flow into the new one. [This PR](https://github.com/dotnet/roslyn-tools/pull/1245/files) is a good example of what to do when a new `release/dev17.4` branch is created that should receive merges from both `main` and the previous release branch, `release/dev17.3`. Old release branch should stop receiving updates from the `main`.
117
117
118
118
6. Set the packages from the new branch to flow into the correct package feeds via the `darc` tool. To do this:
119
-
1. Ensure the latest `darc` tool is installed by running `eng/common/darc-init.ps1`.
120
-
2. (only needed once) Run the command `darc authenticate`. A text file will be opened with instructions on how to populate access tokens.
121
-
3. Check the current package/channel subscriptions by running `darc get-default-channels --source-repo fsharp`. For this example, notice that the latest subscription shows the F# branch `release/dev17.3` is getting added to the `VS 17.3` channel.
122
-
4. Get the list of `darc` channels and determine the appropriate one to use for the new branch via the command `darc get-channels`. For this example, notice that a channel named `VS 17.4` is listed.
123
-
5. Add the new F# branch to the appropriate `darc` channel. In this example, run `darc add-default-channel --channel "VS 17.4" --branch release/dev17.4 --repo https://github.com/dotnet/fsharp`
124
-
6. Ensure the subscription was added by repeating step 3 above.
125
-
7. Note, the help in the `darc` tool is really good. E.g., you can simply run `darc` to see a list of all commands available, and if you run `darc <some-command>` with no arguments, you'll be given a list of arguments you can use.
126
-
8. Ensure that version numbers are bumped for a new branch.
127
-
9. Change needed subscriptions for arcade and SDK:
119
+
120
+
1. To use `darc` you need to be a member of the `dotnetes-maestro-users` entitlement. You can request access at [coreidentity.microsoft.com](https://coreidentity.microsoft.com/manage/Entitlement/entitlement/dotnetesmaes-z54r)
121
+
2. Ensure the latest `darc` tool is installed by running `eng/common/darc-init.ps1`.
122
+
3. (only needed once) Run the command `darc authenticate`. A text file will be opened with instructions on how to populate access tokens.
123
+
4. Check the current package/channel subscriptions by running `darc get-default-channels --source-repo fsharp`. For this example, notice that the latest subscription shows the F# branch `release/dev17.3` is getting added to the `VS 17.3` channel.
124
+
5. Get the list of `darc` channels and determine the appropriate one to use for the new branch via the command `darc get-channels`. For this example, notice that a channel named `VS 17.4` is listed.
125
+
6. Add the new F# branch to the appropriate `darc` channel. In this example, run `darc add-default-channel --channel "VS 17.4" --branch release/dev17.4 --repo https://github.com/dotnet/fsharp`
126
+
7. Ensure the subscription was added by repeating step 3 above.
127
+
8. Note, the help in the `darc` tool is really good. E.g., you can simply run `darc` to see a list of all commands available, and if you run `darc <some-command>` with no arguments, you'll be given a list of arguments you can use.
128
+
9. Ensure that version numbers are bumped for a new branch.
129
+
10. Change needed subscriptions for arcade and SDK:
128
130
1. `darc get-subscriptions --target-repo fsharp`, and then use `darc update-subscription --id <subscription id>` for corresponding channels (e.g. target new VS channel to specific SDK channel, or set up arcade auto-merges to release/* or main branch, depending on the timeline of release/upgrade cycle).
129
131
2. If new subscription needs to be added, the following command should be used `darc add-subscription --source-repo https://github.com/dotnet/arcade --target-repo https://github.com/dotnet/fsharp --target-branch <target_branch> --channel "<target_channel>" --update-frequency everyDay --standard-automerge
130
-
10. Update mibc and other dependencies if needed, refer to https://github.com/dotnet/arcade/blob/main/Documentation/Darc.md#updating-dependencies-in-your-local-repository for more information
131
-
`
132
+
11. Update mibc and other dependencies if needed, refer to https://github.com/dotnet/arcade/blob/main/Documentation/Darc.md#updating-dependencies-in-your-local-repository for more information
132
133
133
134
## Labeling issues on GitHub
134
135
@@ -160,4 +161,4 @@ You need the following permissions to do the above investigations:
160
161
- "Queue builds"
161
162
- "Edit queue build configuration"
162
163
163
-
If anything, reach out to the "First Responders" team.
164
+
If anything, reach out to the "First Responders" team.
0 commit comments