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
Copy file name to clipboardExpand all lines: azure-pipelines.yml
+5-7Lines changed: 5 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -26,14 +26,12 @@ trigger:
26
26
27
27
variables:
28
28
# Release branch for F#
29
-
#Should be 'current' release branch name, i.e. 'release/dev17.10' in dotnet/fsharp/refs/heads/main, 'release/dev17.10' in dotnet/fsharp/refs/heads/release/dev17.10 and 'release/dev17.9' in dotnet/fsharp/refs/heads/release/dev17.9
30
-
#Should **never** be 'main' in dotnet/fsharp/refs/heads/main, since it will start inserting to VS twice.
29
+
#The future "product" gets developed in main, so should be main in main.
30
+
#When servicing branch gets created, this should maintain the mapping between F# servicing and VS servicing branches
31
31
- name: FSharpReleaseBranchName
32
-
value: release/dev18.0
32
+
value: main
33
33
# VS Insertion branch name (NOT the same as F# branch)
34
-
# Should be previous release branch or 'main' in 'main' and 'main' in release branch
35
-
# (since for all *new* release branches we insert into VS main and for all *previous* releases we insert into corresponding VS release),
36
-
# i.e. 'rel/d17.9' *or* 'main' in dotnet/fsharp/refs/heads/main and 'main' in F# dotnet/fsharp/refs/heads/release/dev17.10 (latest release branch)
34
+
# ( for main we insert into VS main and for all *previous* releases we insert into corresponding VS release),
0 commit comments