>
> Apart from the fix, is there any good way to detect this kind of errors in
> individual project reviews?
>
I've added xstatic version checking to our release request validation. Once
this merges, we should be able to automatically catch and error on these types
of conditions:
First of all, thanks for the release team and Radomir.
Apart from the fix, is there any good way to detect this kind of errors in
individual project reviews?
xstatic-cores have new members and all of them are not necessarily super
familiar with the xstatic process.
In addition, updates in xstatic
A fix for it is in review: https://review.openstack.org/577820
On Mon, Jun 25, 2018 at 3:07 PM, Andreas Jaeger wrote:
> On 2018-06-25 14:57, Radomir Dopieralski wrote:
> > Any idea where it took the 1.1.5.0 version from?
>
> git grep 1.1.5 shows at least:
>
> setup.cfg:description =
On 2018-06-25 14:57, Radomir Dopieralski wrote:
> Any idea where it took the 1.1.5.0 version from?
git grep 1.1.5 shows at least:
setup.cfg:description = Angular-Material 1.1.5 (XStatic packaging standard)
xstatic/pkg/angular_material/__init__.py:VERSION = '1.1.5' # version of
the packaged
Any idea where it took the 1.1.5.0 version from?
On Mon, Jun 25, 2018 at 2:38 PM, Doug Hellmann
wrote:
> Excerpts from zuul's message of 2018-06-25 12:14:34 +:
> > Build failed.
> >
> > - xstatic-check-version http://logs.openstack.org/59/
>
Excerpts from zuul's message of 2018-06-25 12:14:34 +:
> Build failed.
>
> - xstatic-check-version
> http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/
> : FAILURE in 1m 31s
> - release-openstack-python release-openstack-python :
