the most proper way to test new versions

[kambala-decapitator]

vcmi-dependencies/README.md

Lines 44 to 48 in dc54d50

	With this approach we will be able to use following flow for new dependencies:
	- change conan/CI settings in this repository as needed
	- run CI in this repository to generate new packages and new release
	- update URL to dependencies in CI/update_conan_dependencies.sh to point to new release
	- open PR in vcmi/vcmi repository that bumps submodule to newest revision of this repository and whatever changes need to be done to source code to use newer package (if any)

Conan recommendation is to use different Conan servers to test new packages:

The way to manage package quality, stage or maturity promotions is by using different server repositories, and the well known developer’s best practices recommend to manage the pipelines by doing promotions (copying) immutable artifacts or packages between those different server repositories, for example copying packages from a staging repository to a production repository once they have passed some quality checks. But it is very important that this promotion does not change in any way those packages, which must be completely immutable, not even changing its user/channel, this is why the above point discourages using user and channel, packages and artifacts must be immutable.

Also see Devops guide