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
* Update docs
* Fix typo in release process documentation
Corrected spelling of 'similar' in the GA releases section.
* Update documentation/release-process.md
Co-authored-by: kkeirstead <[email protected]>
* Add note to revert changes post-release
Added a note to revert changes after release.
---------
Co-authored-by: kkeirstead <[email protected]>
Copy file name to clipboardExpand all lines: documentation/release-process.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,13 @@
23
23
- It can be helpful to create test release branches (e.g. release/test/8.x). Note these branches will trigger warnings because they are considered unprotected release branches and should be deleted as soon as possible.
24
24
- If you created a build from a newly created release branch without a channel, you will get the message 'target build already exists on all channels'. To use this build you need to add it to a channel: `darc add-build-to-channel --id <Build BAR ID> --channel "General Testing"`.
25
25
26
+
## Additional steps for GA releases
27
+
28
+
1.[global.json](../global.json) typically points to `MicrosoftNETCoreApp100Version` and similar, but this will not work for GA releases (since the stable version has not yet been released).
29
+
1. Change `MicrosoftNETCoreApp100Version` to `VSRedistCommonNetCoreSharedFrameworkx64100Version`
1. After the release is finished, this change should be reverted.
32
+
26
33
## Updating dependencies
27
34
28
35
If necessary, update dependencies in the release branch.
@@ -33,7 +40,7 @@ If necessary, update dependencies in the release branch.
33
40
1. Use `darc get-subscriptions --target-repo monitor` to see existing subscriptions.
34
41
1. Use `darc trigger-subscriptions` to trigger an update. This will create a pull request that will update the Versions.details.xml file.
35
42
1. Sometimes an existing subscription needs to be updated. For example, when updating from Preview 5 to Preview 6:
36
-
43
+
1. In some situations the build from the subscription may not be the one you want. You can manually update dependencies using `darc update-dependencies`
0 commit comments