How to create a new release

The following steps explain how to create a release. These steps are done by members of the Firely company.

Common

First, there should be a release for the repository firely-net-common:

• Go to the repository firely-net-common
• Pull the lastest changes on develop
• Check if FhirVersionUtility.cs is still up to date with the latest FHIR releases
• Create a branch release/x.y.z[-beta1-9]
• Change version information in the firely-net-common.props
• Commit this change locally with the message "bumped version to x.y.z[-beta1-9]"
• Tag the commit with the following tagname: vx.y.z[-beta1-9] and push to origin
• Merge release branch into develop
• Change version information in the firely-net-common.props to x.y+1.z-alpha
• Commit the above change with message "Start new development phase: version x.y+1.z-alpha"

firely-net-sdk

• Go to the repository firely-net-sdk
• Pull the lastest changes on develop[-stu3 | r4 | r5]
• Create a branch release/x.y.z[-beta1-9]-[stu3 | r4 | r5]
• Change version information in the firely-net-sdk.props
• Update the submodule firely-net-common to the commit made in the last paragraph with the tag vx.y.z[-beta1-9]
• Commit these changes locally with the message "bumped version to x.y.z[-beta1-9]"
• Tag the commit with the following tagname: vx.y.z[-beta1-9]-[stu3 | r4 | r5] and push to origin
• This will trigger the buildserver to build, test, pack the SDK. You will get an email to approve to release and push it to NuGet.org
• Merge release branch into master
• Merge release branch into develop
• Change version information in the firely-net-sdk.props to x.y+1.z-alpha
• Update the submodule firely-net-common to the latest commit made in the last paragraph (bumped version to x.y.z[-beta1-9]
• Commit the above changes with message "Start new development phase: version x.y+1.z-alpha"
• Optional: delete the release branch

Repeat the above process for r4 and r5.

Create release notes on the release page of Github (https://github.com/FirelyTeam/firely-net-sdk/releases)

Fhir Codegen

When we changed something in the generated Pocos via the fhir-codegen, then we have to make a PR for this change as well and tag that particular commit with the same tag as the sdk release.