From 11f4267c8ebc8206d15ea48b2f3341acebbf6455 Mon Sep 17 00:00:00 2001 From: Oleg Nenashev Date: Mon, 6 Apr 2020 10:26:42 +0200 Subject: [PATCH] Migrate the release flow to https://ci.appveyor.com/project/winsw/winsw-release/ --- DEVELOPER.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/DEVELOPER.md b/DEVELOPER.md index 19f9e49..70e888c 100644 --- a/DEVELOPER.md +++ b/DEVELOPER.md @@ -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.