As discussed in TC PTG[1] and TC resolution[2], we are
dropping the lower-constraints.txt file and its testing.
We will keep lower bounds in the requirements.txt file but
with a note that these are not tested lower bounds and we
try our best to keep them updated.
[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal
This also makes the following two changes to fix the broken CI.
- Switch the python3 job template to unversioned one because
the heat-cfntools project follows an independent release model.
This effectively removes py36 tests.
- Use upper-constraints.txt to build documentation, to avoid pulling
the latest Sphinx which includes a breaking change.
Change-Id: I3c41ed7cd54e8c8d3fad05ea7ac86fc35b9fa4d1
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: Ib6e4e7f89a9990cfb42afa209878812340109ecf
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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.
Also removing the hacking and other related dep from lower-constraints file
as theose are blacklisted requirements and does not need to be present
there.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: Id73106fee729aea32fe37234f3fa7d5263c196aa
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
So we should switch to stestr.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I14ae3879465e622f36fd7bba3f04cb6e0cb7500e
Conform to the PTI for docs builds, add lower-constraints jobs, and use
upper-constraints instead of synced global requirements constraints.
Change-Id: Iaf1b54b35d02dbb733c7782b178e4eb774c02ef6
Ghanshyam Mann