Difference between revisions of "Release schedule and build numbers"
(Created page with "= How to read the ERIKA v3 build numbers = = Release schedule =") |
|||
| Line 1: | Line 1: | ||
| − | = | + | = ERIKA v3 Build codes = |
| − | = Release | + | ERIKA v3 and RT-Druid v3 follow a continuous development and integration process (supported by a local installation of [https://jenkins-ci.org/ Jenkins]). This process merges various repositories (Eclipse, RT-Druid, ERIKA, ...) to create an '''integrated build''' which is afterwards published on the web (for the open-source versions), or used internally. |
| + | |||
| + | Each integrated build is characterized by a unique code, which identifies the exact revisions of each repository involved. The code is composed by two parts: | ||
| + | * '''build code''': a 2-char tag representing the specific build type. The public build is using the tag '''GH''' (meaning '''G'''it'''H'''ub); | ||
| + | * '''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. | ||
| + | |||
| + | |||
| + | = 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. | ||
Revision as of 18:27, 20 December 2017
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 (for the open-source versions), or used internally.
Each integrated build is characterized by a unique code, which identifies the exact revisions of each repository involved. The code is composed by 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.
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.
