12 KiB
Release Process
The release process and building of private binaries is managed by Microsoft Azure Kinect team members.
Released builds are numbered using semantic versioning. The GitHub project and CI builds are not uniquely versioned. Versioning is applied by the private Azure Kinect Packing build system.
The packaging build system may produce multiple builds with the same build number e.g. "1.0.1-beta.0", however only one build of that number will ever be distributed internally or externally for validation or release.
Releases are scheduled on demand based on program needs.
Release Types
Alpha Release
Alpha builds are built using source from the develop branch and are numbered with the
expected release number for current development, such as 1.1.0-alpha.0.
Alpha builds expect heavy churn and are not guaranteed to be backward compatible with each other.
Beta Release
Beta builds are built from the release branches, such as 1.1.0-beta.0.
Release branches are created when that release is being stabilized, at which point only bug fixes and changes required for that release are merged or cherry-picked in to the release branch. Fixes may alternatively be made to the release branch directly and then merged back to the develop branch.
Official Release
Once a beta build has been signed off for release, an official build is created with code from that release branch,
such as 1.1.0
Patch releases
Critical changes to a released build may be made in the release branch to patch an existing release. These changes do not introduce functionality or break compatibility.
Changes are made in the release branch for the existing release, such as release/1.0.x, and are verified with beta
builds for the patch, such as 1.0.1-beta.0, before the patch is signed off and released as 1.0.1
Moving changes between release branches
When a release branch is created it should be created from the develop branch.
Changes may be merged (not squashed) from develop in to a release branch so long as there are no new changes in develop not suitable for that release.
Once develop starts taking changes for the next release, changes must be cherry-picked or made directly in a release branch.
Release branches should always be merged back in to develop (not squashed) after changes have been made there to avoid future merge conflicts.
Our Github repository policy enforces that all pull requests are squashed. Therefore merges between release branches should be done locally, and the results pushed by a repository administrator.
Building a Release Package
The Azure Kinect team will update the packaging build repository to reference the commit of the GitHub Azure Kinect Sensor SDK repository to be released. The Azure Kinect team will schedule an official build of the packaging repository with the correct release version number.
The build will produce an official copy of the SDK with the depth engine and installer. All binaries are signed and the symbols are indexed.
Once a candidate build has been produced, it can be submitted to the Azure Kinect Release pipeline.
The pipeline will:
- Run all release tests.
- Request manual sign off validation.
- Update the documentation resources.
- Tag commit in the Azure Kinect Sensor SDK repository.
- Publish NuGet feeds.
- Request publishing of the MSI installer to the web.
Installer
The Azure Kinect SDK installer provides both open and closed source binaries. The open source binaries are built from this GitHub repo.
Release tags are used by Microsoft to label commits used to create a released build. Checkout the commit that matches the release label to build the desired release version.
Artifacts and Packaging
The following table contains all artifacts that are released in installers and packages. The file paths listed in the table are only representative, within any given package they will be different to match the standards and conventions for those packages. Each unique released artifact is listed in this table only once, although they will potentially appear duplicate times in packages or installers.
| File | MSI/Installer | NuGet | Runtime Debian Package | Development Debian Package | Tooling Debian Package |
|---|---|---|---|---|---|
| LICENSE.txt * | ✅ | ✅ | ✅ | ✅ | ✅ |
| REDIST.txt * | ✅ | ✅ | ✅ | ✅ | ✅ |
| ThirdPartyNotices.txt * | ✅ | ✅ | ✅ | ✅ | ✅ |
| version.txt * | ✅ | ✅ | ✅ | ✅ | ✅ |
| build/msbuild/native/Microsoft.Azure.Kinect.Sensor.targets * | 1️⃣ | ✅ | |||
| build/msbuild/netstandard2.0/Microsoft.Azure.Kinect.Sensor.targets * | 2️⃣ | 2️⃣ | |||
| build/cmake/x64/k4aConfig.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4aConfigVersion.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4aTargets-relwithdebinfo.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4aTargets.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4arecordConfig.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4arecordConfigVersion.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4arecordTargets-relwithdebinfo.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| build/cmake/x64/k4arecordTargets.cmake | 1️⃣ | 1️⃣ | ✅ | ||
| include/k4a/k4a.h | ✅ | ✅ | ✅ | ||
| include/k4a/k4a.hpp | ✅ | ✅ | ✅ | ||
| include/k4a/k4a_export.h | ✅ | ✅ | ✅ | ||
| include/k4a/k4atypes.h | ✅ | ✅ | ✅ | ||
| include/k4a/k4aversion.h | ✅ | ✅ | ✅ | ||
| include/k4arecord/k4arecord_export.h | ✅ | ✅ | ✅ | ||
| include/k4arecord/playback.h | ✅ | ✅ | ✅ | ||
| include/k4arecord/record.h | ✅ | ✅ | ✅ | ||
| include/k4arecord/types.h | ✅ | ✅ | ✅ | ||
| linux-ubuntu/x64/release/libdepthengine.so * | ✅ | ||||
| linux-ubuntu/x64/release/libdepthengine.so.2.0 * | ✅ | ||||
| linux-ubuntu/x64/release/libk4a.so (symlink) | ✅ | ||||
| linux-ubuntu/x64/release/libk4a.so.1.x (symlink) | ✅ | ||||
| linux-ubuntu/x64/release/libk4a.so.1.x.x | ✅ | ||||
| linux-ubuntu/x64/release/libk4arecord.so (symlink) | ✅ | ||||
| linux-ubuntu/x64/release/libk4arecord.so.1.x (symlink) | ✅ | ||||
| linux-ubuntu/x64/release/libk4arecord.so.1.x.x | ✅ | ||||
| linux-ubuntu/tools/x64/release/AzureKinectFirmwareTool | ✅ | ||||
| linux-ubuntu/tools/x64/release/k4arecorder | ✅ | ||||
| linux-ubuntu/tools/x64/release/k4aviewer | ✅ | ||||
| netstandard2.0/AnyCpu/release/Microsoft.AzureKinect.deps.json | 2️⃣ | 2️⃣ | |||
| netstandard2.0/AnyCpu/release/Microsoft.AzureKinect.dll | 2️⃣ | 2️⃣ | |||
| netstandard2.0/AnyCpu/release/Microsoft.AzureKinect.pdb | 2️⃣ | 2️⃣ | |||
| netstandard2.0/AnyCpu/release/Microsoft.AzureKinect.xml | 2️⃣ | 2️⃣ | |||
| windows-desktop/amd64/release/depthengine_2_0.dll * | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4a.dll | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4a.lib | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4a.pdb | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4arecord.dll | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4arecord.lib | ✅ | ✅ | |||
| windows-desktop/amd64/release/k4arecord.pdb | ✅ | ✅ | |||
| windows-desktop/tools/amd64/release/AzureKinectFirmwareTool.exe | ✅ | ||||
| windows-desktop/tools/amd64/release/AzureKinectFirmwareTool.pdb | ✅ | ||||
| windows-desktop/tools/amd64/release/k4arecorder.exe | ✅ | ||||
| windows-desktop/tools/amd64/release/k4arecorder.pdb | ✅ | ||||
| windows-desktop/tools/amd64/release/k4aviewer.exe | ✅ | ||||
| windows-desktop/tools/amd64/release/k4aviewer.pdb | ✅ |