Skip to content

Latest commit

 

History

History
15 lines (10 loc) · 874 Bytes

release_process.md

File metadata and controls

15 lines (10 loc) · 874 Bytes

Overview

This document covers how to release AeroGear services/libraries upstream.

Guidelines

  • Each service/library can be released on its own upstream
  • Release early, release often

Steps

  1. Release the service/library on its own first. It's up to the maintainers of each service to decide how and when to do a release and what level of testing needs to be performed against each release.
  2. Once the new version of a service/library is released, the version vector file should be updated to refect the latest release version of that service/library. The version number for aerogear_mobile_services in that file should be updated as well to reflect the new overarching version of AeroGear Mobile Services.
  3. Create a new PR for the updated release version, and merge.
  4. Create a new tag for the new version of aerogear_mobile_services.