Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: If69cf8d7a867d32e67b4d14428415857ef69d76b
The reason as following:
Create zed branch for client and non-client libs
https://review.opendev.org/c/openstack/releases/+/855929
DNM: dummy change to test gate health
https: //review.opendev.org/c/openstack/python-saharaclient/+/855787/1
Change-Id: I1e803725855fdbb7107a1f1a85acfe345c1103a0
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I53f31d42d3c85f6195ddd4b3197766547958cda8
Python 2 has been deprecated. This patch removes all
traces of six, unicode strings and Python 2 tweaks.
Change-Id: I74696d02558e0fa93ea1775057db13b4f72aed02
In zed cycle, OpenStack projects and oslo lib
has dropped the py3.6 and py3.7 support
- https://governance.openstack.org/tc/reference/runtimes/zed.html
I also decrepated oslo-log < 5.0.0, so we should bump oslo.log>=5.0.0.
Because of oslo.log>=5.0.0 depends on oslo.i18n>=3.20.0 as below, so we
also need to upgrade oslo.i18n.
The conflict is caused by:
The user requested oslo.i18n>=3.15.3
python-saharaclient 1.4.0 depends on oslo.i18n>=3.15.3
castellan 0.16.0 depends on oslo.i18n>=3.15.3
keystonemiddleware 4.17.0 depends on oslo.i18n!=3.15.2 and >=2.1.0
oslo-config 6.8.0 depends on oslo.i18n>=3.15.3
oslo-concurrency 3.26.0 depends on oslo.i18n>=3.15.3
oslo-db 6.0.0 depends on oslo.i18n>=3.15.3
oslo-log 5.0.0 depends on oslo.i18n>=3.20.0
The user requested (constraint) oslo-i18n==3.15.3
The conflict is caused by:
The user requested pbr!=2.1.0 and >=2.0.0
bashate 0.5.1 depends on pbr>=1.6
fixtures 3.0.0 depends on pbr>=0.11
stestr 1.0.0 depends on pbr!=2.1.0 and >=2.0.0
testresources 2.0.0 depends on pbr>=1.8
testtools 2.4.0 depends on pbr>=0.11
python-saharaclient 1.4.0 depends on pbr!=2.1.0 and >=2.0.0
castellan 0.16.0 depends on pbr!=2.1.0 and >=2.0.0
keystoneauth1 3.4.0 depends on pbr!=2.1.0 and >=2.0.0
keystonemiddleware 4.17.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-concurrency 3.26.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-context 2.22.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-db 6.0.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-i18n 3.20.0 depends on pbr!=2.1.0 and >=2.0.0
oslo-log 5.0.0 depends on pbr>=3.1.1
The user requested (constraint) pbr==2.0.0
The conflict is caused by:
The user requested oslo.serialization!=2.19.1 and >=2.18.0
python-saharaclient 1.4.0 depends on oslo.serialization!=2.19.1 and >=2.18.0
keystonemiddleware 4.17.0 depends on oslo.serialization!=2.19.1 and >=1.10.0
oslo-log 5.0.0 depends on oslo.serialization>=2.25.0
The user requested (constraint) oslo-serialization==2.18.0
Change-Id: Iebd0c795dcdd72dac1141cfe18d2dad5201147c1
We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].
I propose to drop this test because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
Change-Id: I60f1f739f25755cd344fe45e76d225712fedc40f
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I46567b4f8c29710c42767fc96ac0176f5f8bc3b7
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: Ifed0f0ac32b4d957e7f0f4a4a41014ea6ea8e815
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: I5d670a37e27605737d1491d8ae0cf7e64c8851b7
The docs requirements migrated to doc/requirements.txt
we need not install things from requirements.txt.
Change-Id: I0749590a9d8b2183ed9c95178541ed85fb19996a
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: I2e83569e917947fb5b381924576ad85a43b792ae
Sem-Ver: feature
As per victoria cycle testing runtime and community goal,
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
Bump lower constraints to make testing work for Focal.
Change-Id: I6354e7abe8eece9e1d9c9005ed90faefd53c65b2
Story: #2007865
Task: #40216
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we don't need it
in lower-constraints.
These changes will help us to drop `mock` from openstack/requirements
Change-Id: I414e2127b313328756c5b15a44b661ea3982a017
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
Set openstackdocs_auto_name to use 'project' as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Depends-On: https://review.opendev.org/729744
Change-Id: I4c81bec463bb61a559ee8941545c16a08b7041f9
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: Ie2e12c6313924f79e7f985897565e0f1d3f03187
Python 3.8 is now our highest level supported python runtime.
This updates the default tox target environments to swap out
py37 for py38 to make sure local development testing is
covering this version.
This does not impact zuul jobs in any way, nor prevent local
tests against py37. It just changes the default if none is
explicitly provided.
Change-Id: I0e1b6b4e5dcddfcba5b14c48493d65da4f083846
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I310c3b8ae925668a1a892892896d0b66a8603fc9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
- Updated CONTRIBUTING.rst per goal guidelines
- Created doc/source/contributor/contributing.rst per goal guidelines
Change-Id: I4a72ec5cec7e48aacc5ce080609fc89f063e7337
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: I96263b774551821745a2345ffb2df3bf2a2dcf05
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: Ib356624acdf10e24f42da957d2f8a7216cfbab3f
Sem-Ver: feature
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I95a49a2941790e0df1fde38f253ba2516959ce80
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8.
Note: The repo has been using an uncapped requirements, so was testing with
hacking 2.0 which disabled the old way of local testing integration.
Remove S367 and S368 since they are not working under python3
"NOTE(Kezar): This checks a good enough if we have only py2.7 supported.
As soon as we'll get py3.x we need to drop it or rewrite. You can read more
about it in dev-list archive, topic: "[hacking]proposed rules drop for 1.0"
Also, hacking now has H304 and H306 which test exactly the same.
Remove hacking and friends from lower-constraints, it's not needed
there.
Change-Id: If60682fb328359ef73dee8f2d89d51410a376677
python-openstackclient removed the usage of glanceclient between 5.1.0
and 5.2.0 (see: https://review.opendev.org/#/c/650374/).
As a consequence, the
openstack dataprocessing image register ...
command is now broken.
This fix means a few requirement bumps to align to OSC 5.2.0,
even though saharaclient 3.0.0 is already released.
Story: 2007501
Task: 39317
Change-Id: I377e0646303aef4984cdd6e4b6587fca9241206b