Skip to content

Release management

Jump to bottom
Chris Hiszpanski edited this page Jun 29, 2019 · 1 revision

Releases are versioned following major.minor.patch according to the following convention:

  • major stepped for API-breaking changes. Software written to interface with AlohaRTC v1 say cannot expect to function without modification with AlohaRTC v2, although maintain backwards compatibility should be attempted where not unreasonably burdensome to do so.

  • minor is stepped for new features which do not warrant a major step.

  • patch is stepped for bug fixes.

Deployment

CircleCI is used for automated deployment. For any commit tagged with a version of the form v1.2.3, CircleCI will build and deploy binaries to s3://get.alohacam.io/release/{VERSION}/{FILENAME} (for example, git tag v1.2.3 will have its armv7 binary available for download at https://get.alohacam.io/release/v1.2.3/alohacam-linux-armv7.

IMPORTANT: Alohacam prompts users to download binaries from get.alohacam.io/release/latest/. The latest alias must be manually updated to point to the newest version, once the version has been tested. This is done via the AWS S3 Console via Redirection Rules.

Copyright 2019 Lanikai Labs. All rights reserved.

Clone this wiki locally