587460bac1
The idea behind the version-map code is to work around a lack of a node that has multiple python3 versions by taking a freeze from one version (say python-3.5) and cloning that to another (say python-3,4). This was written to facilitate the transition from trusty (3.4) to xenial (3.5). With the transition from xenial (3.5) to bionic (3.6) we need to do something similar. To aid the transition it'd be nice to be able to duplicate a 3.5 freeze to both 3.4 *and* 3.6. The current version_map doesn't allow for that. Enhance the version_map code to accommodate this situation. The idea would be to backport this as far as Ocata[1] [1] We need to look again at separating the requirements code from the data Change-Id: I8784509bc162eb6f2e80261bc2d81dbe63ce7989 |
||
|---|---|---|
| .. | ||
| cmds | ||
| tests | ||
| __init__.py | ||
| check.py | ||
| constraints.py | ||
| project_config.py | ||
| project.py | ||
| requirement.py | ||