Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I0098d740761e15f051d4f11f86f566dcf781dde6
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I389899214c01e352b6aa79c0d11e46ee7c59d5a9
These translation sections are not needed anymore, Babel can generate
translation files without them.
Change-Id: I8c0b801ae8e8a79bfeb07e2263c34013ed2fe66a
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: I0cc64c161de97fdfcbf84a3ace270fa32cd3237f
Within 2023.2 python version 3.9 and 3.10 are the
supported python runtimes [1].
[1] https: //review.opendev.org/c/openstack/governance/+/872232
Change-Id: Ia858bd922e47896ca570564f528cf311f9ede3e5
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I840adc214f058f014c1ce837dd045b11a3327cfc
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: Ic510a0f7ffa3d461876d3bb4a37f1026fbafd9dc
In Zed cycle testing runtime, we are targetting to drop the
python 3.6/3.7 support, project started adding python 3.8 as minimum,
example nova:
- 56b5aed08c/setup.cfg (L13)
Also indicates that we support python 3.9.
Change-Id: I539b26e957a1e1a604a77b8e09dcbf63bfececd5
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: I0f76f6a1b052d8cf7e1a27697cfb9cce2fd4475d
Since setuptools v54.1.0[1], the parmeters with dash have been
deprecated in favor of the new parameters with underscore.
This change updates the parameters accordingly to avoid the warnings
like the example below.
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: Ibc4ede8493418470ee5d12a385e1cd749a47f17e
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: Ibf94056375c02ca37536feff5edcf79de39b5890
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: Id0e5435b082b3079e98081adf59e7177675205ea
These were missed in change I3eafc92ba7c7305b1a73d3f96c427ed12c96dbf7.
Change-Id: Idf7148bcf588efbd20352bf2160ecee573156444
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This is now maintained as a Jazzband project [1].
[1] https://github.com/jazzband/prettytable
Change-Id: Id484bf8fe017bf8f6784155462640840b2053677
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
There are only two uses of this. Oddly, we never specified this
dependency directly and were instead relying on it being included
indirectly.
Change-Id: I3229750f3c47689c6b8d9db80a962a755b5a5da9
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
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: I3eafc92ba7c7305b1a73d3f96c427ed12c96dbf7
check_policy_json() common check need [oslo_policy].policy_file
config value and it is better to register those options explicitly
in check_policy_json() in case they are not register by services.
Currently it work as oslo.policy opts are registered via some import
in service side code path for upgradechecks which are not so safe
when these code import path change.
Change-Id: I16fcce119698c7375e4b58558fdce89e78a79a9b
oslotest 1.5.1 is restricted to pbr <1.0 which conflict
with other deps lower constarint for pbr.
Error:
The conflict is caused by:
oslo-i18n 3.15.3 depends on pbr!=2.1.0 and >=2.0.0
oslo-serialization 2.21.1 depends on pbr!=2.1.0 and >=2.0.0
oslo-utils 4.5.0 depends on pbr!=2.1.0 and >=2.0.0
oslotest 1.5.1 depends on pbr!=0.7, <1.0 and >=0.6
https: //zuul.opendev.org/t/openstack/build/cb2bce3b4e004601958b764dfd0737b8
Change-Id: I513262b85a57ce9f81a63bd778fdd7f7be27e485
As part of community goal[1] for migrating the policy file
from JSON format to YAML we need to add upgrade check to
detect any JSON formatted file. That check needs to be
done in each service side which are deprecating the JSON
format. So to avoid duplicate code, this commit add that
check in oslo_upgradechecks and that can be enabled from
service side during they migrate to YAML format.
Service will enable it like below:
_upgrade_checks = (
(_('Policy File JSON to YAML Migration'),
(common_checks.check_policy_json, {'conf': CONF})),
)
Also modify the check() method to accept the **kwargs for checks.
[1] https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Ifa71c20879c964f794a40b981744d95db4ab1602