Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

Workflow and Releases

Jump to bottom
Geoff Gustafson edited this page Dec 5, 2016 · 5 revisions

Releases

The release cadence of the Javascript Runtime for Zephyr (aka ZJS) is aligned with the Zephyr Project cadence of quarterly releases. Each new release of ZJS is updated to the latest released version of Zephyr and includes new features and APIs. Releases are source only, i.e. no binaries are provided and users are expected to build the project themselves.

Features are tracked using GitHub issues labeled with the "feature" label. In general, we keep a more detailed plan for the upcoming release and a high-level one for the later ones. Features planned for a release are assigned to a GitHub milestone, e.g. "0.1".

Branches

The development is organised in the following branches:

  • Master branch. This is where the daily development happens. The master branch should always build but functionality can break occasionally. The master branch is updated frequently with the ongoing mainline of the Zephyr project (and other dependencies, e.g. JerryScript). When getting close (~2 weeks) to a release date, feature inflow is controlled. QA validates the master branch periodically, and the "last known good release" is tagged with the latest tag.

  • Release branch. When the release candidate in master is deemed ready it is branched to a release branch for stabilization. A release branch is always based on a stable version of Zephyr and JerryScript. QA periodically runs release verification on this branch, and the last valid release is indicated with a “stable” tag. Release branches are named according to the ZJS version (e.g. zjs-0.1 etc.). QA does release validation on this branch and the last stable release according to the release criteria is tagged with stable.

Clone this wiki locally