- django-4-ugettext_lazy-is-removed.patch
    - django-4-django.conf.urls.url-is-removed.patch

watcher-dashboard 7.0.0.0rc1 release candidate

meta:version: 7.0.0.0rc1
meta:diff-start: -
meta:series: yoga
meta:release-type: release candidate
meta:pypi: no
meta:first: no
meta:release:Author: Elod Illes <elod.illes@est.tech>
meta:release:Commit: Elod Illes <elod.illes@est.tech>
meta:release:Change-Id: I4ab49e5d9aea81166e8074366c49247400666beb
meta:release:Code-Review+1: chenker <chen.ke14@zte.com.cn>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

watcher-dashboard 6.0.0.0rc1 release candidate

meta:version: 6.0.0.0rc1
meta:diff-start: -
meta:series: xena
meta:release-type: release candidate
meta:pypi: no
meta:first: no
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: I84a95e636a7e750c2d10f886ed57765576dad63d
meta:release:Code-Review+1: chenker <chen.ke14@zte.com.cn>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Workflow+1: Elod Illes <elod.illes@est.tech>

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Ifd0557060d055aa07b34320808b2360387a226cb

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: Iee515e29541c6957db520339fa923a59a392ff6e

Change-Id: I79cd70085e9e423fa3a7835e4a7fbd2b0cbf4922

Change-Id: I674eea6d66a78f524fdd2b505b4788450130a0e4

Coverage report job for watcher dashboard must have been
broken for an extensive amount of time. This patch
fixes it.

Change-Id: I3f0ec731d28d0f55c4378038237dc91b5c548ed5

The patch bumps min version of tox to 3.18.0 in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23

Change-Id: I83ee292b6d7440f7543ef85d7eed82940ee9745d

This prevents having to duplicate the -c{} deps argument
across all environments in tox.ini

Change-Id: I681688df779557654b001caf33ca6ffbda08f43b

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: I9c293e6055aa7ae50a2d3b6537d19033bf380bc2

Change-Id: I0d5115c037f89aede2434442439f4ad465700338

The name is a positional parameter in create() of audit,
but this parameter is not defined when calling from the
audit template. This patch fix it.

Related Bug: #1930565
Change-Id: Id18945b881d150f972dbbd5522010be0157fba17

    /usr/lib/python3/dist-packages/openstack_dashboard/local/enabled.
  * Add Breaks: python3-django-horizon (<< 3:19.2.0-2~).

Moving on py3 as the default runtime for tox to avoid to update
this at each new cycle.

Change-Id: I00108fb70f077eeda092c9124f37df51860df370

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: I0573f72eb92ddda5392dbf78260a18b17a8d75af

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: I9308030b0a16f9a7e085b3e64230cd92dda6ad83