5af4478fb2
This makes the RPC version support three elements, adding a "revision" in addition to the major and minor version. The revision would always be zero for the master branch of a service, but could be incremented for stable versions. This provides us some room to backport fixes that affect RPC versions in such a way that would avoid breaking the version lineage for systems running stable versions that may some day be involved in a rolling upgrade to a version from master. I didn't find any tests for version_is_compatible(), so I added some for existing version scenarios, as well as new ones with revisions. They also serve to validate that this doesn't break anything for code using two-element versions (the expectation is that two-element versions will still be used everywhere until a third is needed). Porting chages from Change-Id I239c17a3e305f572493498c4b96ee3c7514c5881 to oslo-incubator Change-Id: I4fa7b0be14a7afba36136a746b76036355f119b2 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_exception_serialization.py | ||
| test_expected_exceptions.py | ||
| test_notifier.py | ||
| test_pool.py | ||
| test_rabbit.py | ||
| test_rpc_client.py | ||
| test_rpc_dispatcher.py | ||
| test_rpc_server.py | ||
| test_target.py | ||
| test_transport.py | ||
| test_urls.py | ||
| test_utils.py | ||
| utils.py | ||