ferecaptain.blogg.se - Indy 440 pipe

INDY 440 PIPE INSTALL
INDY 440 PIPE CODE

for the project: source code version would be X.Y.Z, debian package version X.Y.Z~rcN.Bump version locally to X.Y.Z, commit and push as the release commit to remote.Start release candidate pipeline manually.Note If any of the following steps fails new release candidate should be prepared.

different versions in migrations scripts.

setup.py: different versions of indy-plenum dependency.

Master and Stable share the same versioning scheme.

INDY 440 PIPE INSTALL

If you install indy-node (either from pypi, or from deb package), the specified in setup.py version of indy-plenum is installed.

Each dependency (including indy-plenum) has a strict version (see setup.py).

During release preparation phase (release / hotfix workflows) version includes pre-release segment rcN, where N>=1 and set in the source code by developers.

In the source code it is just equal to 0 always.

During development phase version includes developmental segment devN, where N is set for CD pipeline artifacts as incremented build number of build server jobs.

Version is bumped for new releases / hotfixes either manually or using bump_version.sh script.

Version is set in the code (see _version_.json).

Please note, that we are using versioning that satisfies PEP 440 with release segment as that satisfies SemVer as well.

It’s not guaranteed that that this code is stable enough.

indy-node deb package from xenial masterĬontains the latest changes (from master branch).

Is one and the only official stable release that can be used for production (stable version).

indy-node deb package from xenial stable.Using deb packages is recommended way to be used for a test/production pool on Ubuntu.PyPI artifacts can be used for development experiments, but not intended to be used for production.indy-plenum deb package in xenial stable (copied from stable-latest).indy-node deb package in xenial stable (copied from rc-latest).indy-node deb package in xenial stable-latest (re-packed from rc-latest).indy-plenum deb package in xenial stable-latest.indy-plenum deb package in xenial rc (copied from rc-latest).indy-node deb package in xenial rc (copied from rc-latest).indy-node deb package in xenial rc-latest.indy-plenum deb package in xenial rc-latest.all artifacts include pre-release segment rcN in their version.indy-plenum deb package in xenial master (copied from master-latest).indy-node deb package in xenial master (copied from master-latest).indy-node deb package in xenial master-latest.indy-plenum deb package in xenial master-latest.all artifacts include developmental release segment devN in their version.What artifacts are produced after each push