bf72a50942
hacking is not capped in g-r and it is in blacklist for requirement as hacking new version can break the gate jobs. Hacking can break gate jobs because of various reasons: - There might be new rule addition in hacking - Some rules becomes default from non-default - Updates in pycodestyle etc That was the main reason it was not added in g-r auto sync also. Most of the project maintained the compatible and cap the hacking version in test-requirements.txt and update to new version when project is ready. Bumping new version might need code fix also on project side depends on what new in that version. If project does not have cap the hacking version then, there is possibility of gate failure whenever new hacking version is released by QA team. Example of such failure in recent release of hacking 1.1.0 - http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html Change-Id: I50448c8cd470fbb5266a728a9b5ed2e46e1448a2
13 lines
193 B
Plaintext
13 lines
193 B
Plaintext
hacking>=1.0.0,<1.1.0
|
|
|
|
coverage>=3.6
|
|
fixtures>=0.3.14
|
|
mock>=1.0
|
|
python-subunit
|
|
oslotest>=1.2.0
|
|
os-testr>=1.0.0
|
|
testrepository>=0.0.18
|
|
testscenarios>=0.4,<0.5
|
|
testtools>=0.9.34
|
|
posix_ipc>=0.9.8
|