-
Notifications
You must be signed in to change notification settings - Fork 104
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
15 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,19 @@ | ||
# Release steps | ||
|
||
1. Switch branches to 2.x | ||
2. Merge in commits/branches for the release | ||
3. Update version.json and commit with "Release {version}" | ||
4. Wait for tests to pass in CI | ||
Use https://github.com/dotnet/Nerdbank.GitVersioning/blob/master/doc/nbgv-cli.md | ||
|
||
Next, do the release: | ||
To create release branch in master: | ||
|
||
```bash | ||
git tag -a v2.0.4 -m "Release 2.0.4" | ||
git push origin v2.0.4 | ||
msbuild /p:Configuration=Release /p:PublicRelease=true | ||
rm -r packages | ||
for f in packages/Release/*; do nuget push $f; done | ||
``` | ||
``` | ||
nbgv prepare-release | ||
nbgv tag | ||
``` | ||
|
||
And push branches and tags. | ||
|
||
To make a servicing release: | ||
|
||
* Bump version.json | ||
* `nbgv tag` | ||
|
||
And push branches and tags. |