[openstack-dev] [Horizon] How do we move forward with xstatic releases?

Matthias Runge mrunge at redhat.com
Thu Mar 10 07:23:14 UTC 2016

On 09/03/16 19:52, Michael Krotscheck wrote:
> On Wed, Mar 9, 2016 at 7:58 AM Monty Taylor <mordred at inaugust.com
> <mailto:mordred at inaugust.com>> wrote:
>     > SOLUTION 4: vendor the javascript
>     >
>     > Heh.
>     Heh indeed.
>     SOLUTION 4.alt: use npm/bower instead of xstatic to pull the javascript.
> +1. Let's move the codebase forward, instead of continuing to build
> hacky workarounds for poor past architectural decisions.
Coming from a distro perspective:

move to proper packages for static file management. I mean, they need to
be built anyways.

It has been mentioned, xstatic packages can block the gate. We currently
control xstatic package releases, thus we can roll back, if something
goes wrong.

If we're pulling directly with npm/bower, someone from the outside can
break us. We already have the situation with pypi packages.
With proper packages, we could even use the gate to release those
packages and thus verify, we're not breaking anyone.


Matthias Runge <mrunge at redhat.com>

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
                    Michael O'Neill

More information about the OpenStack-dev mailing list