-
Notifications
You must be signed in to change notification settings - Fork 990
HowTo: create a release
Igor Velikorossov edited this page Oct 31, 2019
·
7 revisions
-
Merge the current master int a release branch
git fetch --all # checkout branches git checkout -B "release/3.0" "origin/release/3.0" git checkout -B master "origin/master" # merge git merge --no-ff --strategy=ours "release/3.0"
-
❗️ Carefully review the changes
-
Push the changes.
# switch branches and push git branch -D "release/3.0" git checkout -b "release/3.0" git push -u --force --recurse-submodules=check --progress "origin" "release/3.0"
-
Update the branding in eng/Versions.props
-
Create a release tag and push it
- Browse to Core SDK latest or Core setup latest and look at the build number and commit of winforms that’s in core-sdk
- Checkout the release/3.0 branch for winforms
- Create a new tag like this: git tag -a 4.8.0-preview6.190603.7 -m "preview 6 tag"
- 4.8.0 because it matches all our previous release tags
- Change the preview number to the current release
- 190603.7 because that matches the build number on the site above (if the Date Produced column for the "winforms" row is old, you'll need to wait for the core-setup build to finish)
- Push the tag to the origin like this:
git push origin 4.8.0-preview6.190603.7
- browse to https://maestro-prod.westus2.cloudapp.azure.com/
- select the correct channel
- select dotnet/core-setup
- The
winforms
line shows what commit made it into core-setup, that's the commit that needs to be tagged. Use the build number from that page to figure out what goes in the tag
- Dependencies
- ARM64