adding executables build for

README.md

@@ -2,19 +2,22 @@
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
-
 ***Chains:***
+
 * [***Mainnet information***](./docs/common/mainnet/001-mainnet.md)
 
 * [***Testnet (Mainnet-beta) information***](./docs/common/testnet/001-testnet.md)
 
 ## Introduction
 
-**rarimo-core** is a blockchain built using Cosmos SDK and Tendermint and created with [Ignite CLI](https://ignite.com/cli).
+**rarimo-core** is a blockchain built using Cosmos SDK and Tendermint and created
+with [Ignite CLI](https://ignite.com/cli).
 
-Based on Tendermint + Cosmos SDK blockchain core the main goal is to provide validated information about different cross-chain operations.
+Based on Tendermint + Cosmos SDK blockchain core the main goal is to provide validated information about different
+cross-chain operations.
 
 Documentation:
+
 * [Rarimo core modules business logic](./x/README.md)
 * [Bridge contract architecture](./docs/common/contracts/001-contracts.md)
 * [Bridging flow overview](./docs/common/bridging/001-bridging.md)
@@ -25,22 +28,41 @@ Documentation:
 ### Install
 
 Use
+
 ```shell
 ignite chain build
 ```
 
-If it fails in generate proto stage with error on etheremint .proto files just re-execute that command or try to add `--clear-cache` flag.
+If it fails in generate proto stage with error on etheremint .proto files just re-execute that command or try to
+add `--clear-cache` flag.
 
 ### Generate proto files
 
 Use
+
 ```shell
 ignite generate proto-go
 ```
 
-If it fails in generate proto stage with error on etheremint .proto files remove `./proto/ethermint` package and execute command again.
+If it fails in generate proto stage with error on etheremint .proto files remove `./proto/ethermint` package and execute
+command again.
 DO NOT FORGET TO RETURN DELETED PACKAGE.
 
+## Versioning
+
+Rarimo core leverages on the following branches:
+
+- `master` branch with vanilla core version
+- `mainnet-beta` branch with testnet core with all testnet upgrades
+- `mainnet` branch with mainnet core with all mainnet upgrades
+
+For the tags we are using an approach when stable releases with `vx.x.x` tag has only the `mainnet` core. On the other
+side `mainnet-beta` releases are build under `vx.x.x.rc-x` tag. For the master branch releases only hash tagged images
+will be provided.
+
+Before creating the `mainnet` release be sure that it includes all unreleased changes from `mainnet-beta` and then
+select the corresponding version number that will cover all released tags on `mainnet-beta`.
+
 ## Learn more
 
 - [Ignite CLI](https://ignite.com/cli)