# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
hacking>=3.0,<3.1.0 # Apache-2.0
unittest2>=1.1.0 # BSD
coverage>=4.5.1 # Apache-2.0
testtools>=2.3.0 # MIT
stestr>=2.0.0 # Apache-2.0
oslotest>=3.3.0 # Apache-2.0

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
hacking>=3.0.1,<3.1.0 # Apache-2.0
unittest2>=1.1.0 # BSD
coverage>=4.5.1 # Apache-2.0
testtools>=2.3.0 # MIT
stestr>=2.0.0 # Apache-2.0
oslotest>=3.3.0 # Apache-2.0

Fix hacking min version to 3.0.1
Fix hacking min version to 3.0.1

flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.

Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.

To avoid similar gate break in future, we need to bump the hacking min
version.

- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html

Change-Id: Ia5b166e3a45d38f98e18f1f7f85bb5352e4de4ae
