1. Can anyone help with the following tasks:

• We need to get cake build script to build the gem package as it isn't built at present.
• We need to get cake build script to build the tfs task as it isn't build at present.

2. We need to get all of the build assets being pushed automatically to their respective deployment channels, on every commit push. Can we agree on the following strategy:

• In order to issue a "stable" release, we will tag a commit on master with a stable number.
• Every other commit not tagged with a stable number, and irrespective of branch, will produce an "Unstable" release.

If so we need to:

• Configure gitversion to produce stable / unstable version numbers as per the above.
• Amend the build so that stable assets (i.e of the back of a stable build) are pushed to their stable deployment channels (i.e nuget.org etc)
• Ament the build so that "unstable" assets (everything that isn't a stable build are pushed to their unstable / pre-release deployment channels (i.e appveyor ci nuget feed etc)

Note: There appears to be a cake script for deployments` that does a lot of what we need already, but it's not clear to me when this runs or if someone executes it manually or something. Perhaps someone could clarify whether its still used and how.

We have PR's waiting in the wings, and issues because people can't find the latest packages where they are expecting, and this is because we haven't been able to get a handle on the release process or are too reliant on manual intervention.

See several of the bottom comments here for background.

The assets we need to be pushing (Please amend appropriately) are as seen here:

• NuGetCommandLineBuild --> NuGet.org
• NuGetRefBuild --> NuGet.org
• NuGetExeDotNetCoreBuild --> NuGet.org
• NuGetTaskBuild --> NuGet.org
• NuGetExeBuild --> Chocolatey.org
• GemBuild --> ?
• GitVersionTfsTaskBuild--> ?
• zip --> Docker Hub
• zip-dotnetcore --> Docker Hub