Release schedule and build numbers

Jump to: navigation, search

ERIKA v3 Build codes

ERIKA v3 and RT-Druid v3 follow a continuous development and integration process (supported by a local installation of Jenkins).
This process merges various repositories (Eclipse, RT-Druid, ERIKA, ...) to create an integrated build which is afterwards published on the web site (for the open-source versions), or provided to customers.

Each integrated build is characterized by a unique code, which identifies the exact revisions of each repository involved. The code is composed of two parts:

  • build code: a 2-char tag representing the specific build type. The public build is using the tag GH (meaning GitHub);
  • build number: a natural number which is increased every build.

As an example, GH14 refers to the 14th build including the public GitHub code.

A few important things to note:

  • If you consider 2 builds, GH13 and GH14, then you can conclude that GH14 is newer than GH13.
  • The build numbers are related to the build code. That is, given builds XX13 and GH14 it may not be true that GH14 is newer than XX13, because the two numbers have no relationship each other being based on two different build codes.

Stable versions

Note that, similarly to the development of the Linux kernel, we don't keep a proper "unstable" tree.
Despite our continuous integration system runs most tests whenever some code is committed to a repository, the various versions on GitHub (except those specifically released on the website) have not been fully tested and therefore could still have some issue.
If you want to work on a stable version, the best practice is to download the Eclipse RT-Druid package, which contains a source copy of the RTOS in the plugins/ section.

Release Schedule

We plan to release a new "official" version of ERIKA v3 roughly every 6 months.

As of today, we are not aiming to mark them with a specific version number. Likely we will continue to refer to the build code.