github
/
winsw
mirror of https://github.com/winsw/winsw
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #480 from winsw/release-flow-miigration 

Migrate the release flow to https://ci.appveyor.com/project/winsw/winsw-release/
pull/477/head
Oleg Nenashev 2020-04-06 10:38:28 +02:00 committed by GitHub
parent 195966a9f4 11f4267c8e
commit db6f2074d0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
DEVELOPER.md
View File

@ -17,16 +17,16 @@ Versions generated by the CI instances are **NOT** aligned with the release vers
### Releasing to GitHub and NuGet
Releases are being performed to 3 locations: GitHub, NuGet, and Jenkins Maven Repository.
For all these releases we use binaries being created by the special AppVeyor Job ([winsw-release](https://ci.appveyor.com/project/oleg-nenashev/winsw-release)).
For all these releases we use binaries being created by the special AppVeyor Job ([winsw-release]https://ci.appveyor.com/project/winsw/winsw-release/)).
Here are the release steps:
1. Integrate all pull requests you want to release to the master branch.
1. Update [CHANGELOG](./CHANGELOG.md) and push changes to the master.
1. Wait till the [AppVeyor build](https://ci.appveyor.com/project/winsw/winsw) finishes for the last commit.
1. Go to the [winsw-release job page](https://ci.appveyor.com/project/oleg-nenashev/winsw-g2fwp).
1. Go to the [winsw-release job page](https://ci.appveyor.com/project/winsw/winsw-release/).
1. If you are doing a release with a new feature, bump the second digit in the _Version_ setting (e.g. to `2.N.${build}`) and change the next build number to `0`. In such case the version in assembly info will be `2.N.0`
1. Run the [winsw-release](https://ci.appveyor.com/project/oleg-nenashev/winsw-g2fwp) build.
1. Run the [winsw-release](https://ci.appveyor.com/project/winsw/winsw-release/) build.
Once it completes, ensure the version is correct.
1. Click on the _Deploy_ button for the build.
Then deploy changes to _GitHub Releases_ and NuGet using the available publishers.