Development Cycle

A typical development cycle

1. Develop new feature on branch. When pushed, this triggers a build at TeamCity without release. Perfect to check if the code just works on my machine
2. Merging feature to master will trigger a beta build and release, for more info see Nuget.org/digipost-api-client-dotnet for versions released.
3. If the new version breaks existing API, documentation must be updated, and can be found in the docs folder of the project. Do not edit the documentation directly from here if it involves changing code. This must first be done in the documentation-regression-tests project and copied to the docs. This may seem redundant, but errare humanum est.
4. Trigger release build in TeamCity.
5. Create release note for the release!